Every synchronisation records what happened to the collection order. You see this in the timeline of the collection order and, if you use the API, as an event code in the events field of the response. Per synchronisation one event about the amount is recorded for a collection order, possibly followed by an event about the status and by skipped invoices.
Without a settlement or payment promise
| Code | When | What happens |
|---|---|---|
| N1 | New item, no collection order yet, amount above 0 | New collection order started |
| NP1 | Same as N1, but the item is paused in your accounting system | New collection order started and paused right away |
| CS1 | Amount equal | Nothing changed; data and variables refreshed. Timeline: The amount has stayed the same |
| PP1 | Amount lower | Difference recorded as a payment on the invoice lines |
| PP2 | Amount lower and an invoice is missing from the delivery | Payment recorded and the missing invoice removed from the collection order |
| CI1 | Amount higher | Invoice lines replaced by the new set |
| PF0 | Amount 0 or negative | Collection order set to Paid; open messages and paylinks closed |
| PF1 | Collection order missing from the complete list (only with delivery by file or accounting integration) | Collection order set to Paid |
| PR1 | Invoice was paid through POM within the payment respite, but is still in your list | Invoice skipped; no new collection order starts |
Status changes
| Code | When | What happens |
|---|---|---|
| SA1 | Status active, collection order was paused | Collection order resumed. Timeline: Flow resumed because this collection order was unblocked in the accounting system |
| SP1 | Status pause, collection order was active | Collection order paused |
| SW1 | Status withdraw | Collection order withdrawn |
| SPS1 | Status pause during a settlement | Settlement cancelled, collection order paused |
| SWS1 | Status withdraw during a settlement | Settlement cancelled, collection order withdrawn |
| SPP1 | Status pause during a payment promise | Promise cancelled, collection order paused |
| SWP1 | Status withdraw during a payment promise | Promise cancelled, collection order withdrawn |
During a settlement
The portal compares the amount from your list with the invoice total excluding recent payments. The terms are then updated.
| Code | When | What happens |
|---|---|---|
| CSS1 | Amount equal, or lower but nothing changed since the previous synchronisation | Nothing changed |
| PTF1 | Paid amount is exactly the next term | Term set to paid |
| PTP1 | Paid amount is less than the next term | Term lowered by the paid amount |
| PTF2 | Paid amount is more than the next term | Term set to paid, rest passed on to the next term(s) |
| CIS1 | Amount higher | Invoice lines replaced, settlement cancelled |
| PFS0 | Amount 0 or negative | Collection order set to Paid, settlement closed |
| PFS1 | Collection order missing from the complete list (only with file or accounting integration) | Collection order set to Paid, settlement closed |
With an extra repayment several term events can be recorded in a row, one per (partly) paid term. For example, if a customer pays 100 euros on a settlement of three terms of 40 euros, you see PTF2, PTF2 and PTP1: terms 1 and 2 set to paid, term 3 lowered to 20 euros.
During a payment promise
| Code | When | What happens |
|---|---|---|
| CSP1 | Amount equal, or lower but nothing changed since the previous synchronisation | Nothing changed |
| PPF1 | Paid amount is exactly the remaining promised amount | Promise fulfilled; follow-up action from the profile for the remaining balance |
| PPL1 | Paid amount is less than the promised amount | Payment recorded, promise continues |
| PPM1 | Paid amount is more than the promised amount | Promise fulfilled; follow-up action from the profile for the remaining balance |
| CIP1 | Amount higher and the profile breaks the promise on an increase | Invoice lines replaced, promise broken, follow-up action carried out |
| CIP2 | Amount higher and the profile lets the promise continue | Invoice lines replaced, promise continues |
| PFP0 | Amount 0 or negative | Collection order set to Paid, promise fulfilled |
Good to know
- One synchronisation can contain several codes in the API response: the event about the amount, then a status change (SA1, SP1, SW1 or the variant with settlement or promise) and one PR1 per skipped invoice.
- If a collection order is started through a regular call or upload instead of through Collection Sync, you do not see these codes.