Entities
Learn how Monite API Partners can manage their customers.
Overview
Entities represent the customers of Monite API partners and can be either organizations or individuals (persons).
An entity registers its operations and stores financial documents (such as payables or bank transactions) via the partner’s applications. Those financial documents are in turn stored and processed by Monite.
Learn more about entities, entity users, and the Monite account structure.
Create an entity representing your customer
To create a new entity, call POST /entities
. The entity can be either an organization or an individual:
Organization
Individual
Explanation of the request fields:
-
For
organization
entities:business_structure
- Required for EU and US entities to accept payments. Possible values:- EU:
incorporated_partnership
,private_corporation
,public_corporation
,unincorporated_partnership
- US organizations:
multi_member_llc
,private_corporation
,private_partnership
,public_corporation
,public_partnership
,single_member_llc
,sole_proprietorship
,unincorporated_association
- EU:
-
For
individual
entities:id_number
- Required for Dutch individuals to accept payments. The person’s Burgerservicenummer (BSN) or Dutch Citizen Service Number.ssn_last_4
Required for US individual to accept payments. The last four digits of the person’s Social Security Number (SSN).
-
tax_id
- the taxpayer registration number. If the entity will use Monite’s Account Receivable API, eithertax_id
or VAT ID, or both must be specified.- In France, the
tax_id
is the SIREN/SIRET number. - In the Netherlands, the
tax_id
is the Dutch Business Register number (KVK). - A Liberian entity’s tax number must be specified as its VAT ID rather than the
tax_id
.
- In France, the
A successful response returns the unique ID assigned to the created entity, along with the rest of the entity information:
Notes:
-
Spanish entities registered in the Canary Islands must use the country code
IC
instead ofES
in their address.Spanish entities registered in Ceuta and Melilla must use the country code
EA
instead ofES
. -
Entities can use Monite payment rails to accept and send payments. For this, the entity must be onboarded. Providing as much information as possible during the entity’s registration process will make the onboarding process smoother.
-
After an entity is created, you must also add its bank accounts.
-
Entities of the
organization
type must also add information of the legally responsible individuals associated with the organization. See the Persons page for details.
Upload entity logo
You can provide the entity logo for use in the PDF documents generated by the entity (such as Accounts Receivable invoices and credit notes). The logo will also appear on the payment page if the entity uses Monite payment rails.
The logo image can be PNG or JPG up to 10 MB in size.
To upload the logo for an entity, call PUT /entities/{entity_id}/logo
with a multipart/form-data
body containing the image in the file
field:
The specified logo is stored on Monite servers, and the successful response returns the logo file information:
The logo file information will also returned in the logo
response field when you retrieve entity information with GET /entities/{entity_id}
or similar requests.
You can update the logo at any time later by uploading a new logo. You can also delete the logo by sending a DELETE
request to the /entities/{entity_id}/logo
.
List all entities
To get information about all the entities managed by the partner, call GET /entities
. This endpoint supports the standard pagination, sorting, and filtering parameters.
Get a single entity
To get information about a specific entity, call GET /entities/{entity_id}
:
Update entity information
To update the details of an existing entity, call PATCH /entities/{entity_id}
:
Access the current user’s entity
If you use entity user tokens to authenticate Monite API requests, the following endpoints let you access the current user’s entity without providing its ID:
GET /entity_users/my_entity
- get entity information.PATCH /entity_users/my_entity
- update entity information.
To use these endpoints, the entity user in question must have a role with the entity.read
and entity.update
permissions, respectively.