The Customer party object
When you create a sales invoice, sales credit note, or proforma invoice, you pass the buyer's details inline in the accounting_customer_party object. This page documents validation rules for document create payloads — not a standalone customer profile API.
On sales documents, the supplier (accounting_supplier_party) is set automatically from the {profileId} business profile—do not send it. On purchase documents, the customer (accounting_customer_party) is set from the profile—see Supplier validation for the party you must send.
Customer rules are not the same as business profile or supplier rules.
Before you start
Decide whether the customer is a business or an individual. On sale documents, Marmin infers this from
scheme_agency_id:EIDorPASmeans individual; all other values (or omission) mean business.Check whether the customer's address is in the UAE (
country_code=AE) or outside the UAE.Registration details are optional. You do not need to send
scheme_agency_id,company_id,authority_name, orpassport_issuing_country_codeunless you want to include them.Keep registration and VAT separate:
Registration number (
company_id) — trade license, cabinet decision, Emirates ID, passport number, or other identifier (only when you send registration details)VAT number / TRN (
party_tax_scheme.company_id) — 15-digit UAE tax registration number
Request fields
Fields on accounting_customer_party when creating or resubmitting sale documents. Rows are ordered Required → Conditional → Optional.
Do not send on create: profile_id (use only when referencing an existing registered profile; returned in responses). Do not confuse with business_profile_id in the URL path.
Request postal_address
Request party_tax_scheme
Endpoint identification
endpoint_id and endpoint_scheme_id are required on accounting_customer_party for every sale document, credit note, and proforma invoice. Marmin no longer defaults the buyer endpoint when either field is omitted — you must set the correct values explicitly.
UAE e-invoicing compliant buyer (Peppol-registered): use the buyer's 10-digit TIN as endpoint_id with endpoint_scheme_id 0235.
Special scenarios: use the FTA substitute participant identification from the table below.
Use row 3 when the buyer has not implemented e-invoicing or does not have a Peppol endpoint. Previously Marmin applied 9900000098 automatically when the endpoint was omitted — that default no longer applies.
Response fields
Fields returned on accounting_customer_party in document retrieve/list/create responses.
Core fields
Response postal_address
Conditional field rules
Validation by scenario
UAE business customer
Non-UAE business customer
UAE individual customer
If you include registration details
Registration fields are optional. If you choose to send scheme_agency_id, the following rules apply:
See Get Registration Types section for details.
Using this object on sale documents
Include these fields on accounting_customer_party when you create or resubmit a sales invoice or sales credit note. The same rules apply on proforma invoices for the customer party.
For export transactions, see Export transaction with delivery.
