PINT Mapping
Every field on a filed invoice has to come from somewhere in your data. This screen holds that decision, one row per field. Completing it is a required step after the ERP is connected — invoices are not filed against a mapping that was never finished — but it starts from one click, and most entities change little after that.
Completing it: pre-fill, then review
Pre-fill defaults sits at the top of the screen. Click it and every row is populated with the standard mapping for the accounting system you connected — the paths a normal Xero, QuickBooks or Zoho setup uses.
Then read down the list and check each field. Pre-filling is a starting point, not an answer: it knows the shape of your ERP, not where your business decided to keep things. The two minutes spent confirming each row is what stops a run of invoices being rejected for the same reason.
- Connect the ERP to the entity.
- Open PINT Mapping and click Pre-fill defaults.
- Review every field and correct anything that reads from the wrong place.
- Mark any field your system simply does not hold as Will be provided at invoice level.
- Save. Invoices arriving from then on are mapped this way.
What a mapping is
On the left, the field the invoice needs — the buyer's tax number, the line quantity, the invoice date. On the right, where to read it from in your own invoice. The defaults follow each system's normal layout, which is why a standard Xero or Zoho setup works immediately.
You would change one when your business keeps something in an unusual place: a TRN in the second custom field rather than the first, a trade licence in a field meant for something else, a description that lives on the item instead of the line.
The three kinds of field
| Kind | What it means |
|---|---|
| Mandatory | Fields every invoice must carry: number, date, currency, buyer, totals, lines. Defaults are filled in for your system and normally need no attention. |
| Conditional | Fields some invoices need: legal registration details, a payment means, item classification. Left unset until an invoice needs one. The exchange rate row is locked while the entity is set to use the Central Bank rate, and becomes yours to configure when it is not. |
| Will be provided at invoice level | Available on every field, and the answer when your system does not hold one at all. The value stops being read from the ERP; the invoice waits on Staged Invoices until you type it in and submit. |
“Will be provided at invoice level”
Every field on this screen carries this option. Some PINT fields have no home in an ordinary accounting system — a billing frequency for a continuous supply, a customs declaration reference on an export — and rather than inventing a place for them in your ERP, you tell the platform to ask you for them instead.
Choosing it changes what happens when the invoice arrives. The value no longer has to come from the ERP mapping, so the invoice is read in and then held on Staged Invoices instead of continuing. You supply the missing value there and submit the invoice; only then does it carry on to validation and the Peppol network.
How many invoices this affects depends on the field. If it is one every invoice must carry, every invoice will stage and wait for you. If it is a conditional field, only the invoices that actually trigger it wait — a plain domestic tax invoice is not held for an export reference it could never use.
The staging screen, and what submitting from it does, is on Sending invoices.
Changing a mapping later
A change applies to invoices processed from then on. It does not retrospectively re-file anything already sent — a filed invoice is a filed document, and re-filing it under a new mapping would be a second submission of the same invoice.
If a mapping was wrong on something already sent, correct it here and issue a credit note for the document that went out, rather than expecting the original to be rewritten.
Related
The per-system defaults, field by field, are listed on ERP prerequisites — each entry names the path it reads, which is exactly what you would repoint here.