Reconcile activity

Reconciliation should explain how a payment in your system became a financing obligation in Axiym and how that obligation changed over time.

Build a stable identifier chain

Store these relationships when they first become available:

Do not use a description, amount, or timestamp as the only join key.

Reconcile current state

For each client and accounting period:

1. List the client's receivables and follow every page.
2. Retrieve individual receivables when detailed disbursement or repayment transactions are required.
3. Retrieve the client's credit accounts.
4. Join those resources to your original payments, accepted financial operations, and stored events.
5. Investigate missing, duplicated, or contradictory records before closing the period.

Values to compare

At minimum, compare:

• the funded payment amount and initialPrincipal;
• currentPrincipal and recorded repayment transactions;
• repaymentAmount and the total obligation represented in your ledger;
• credit-account availableBalance and principalOutstanding; and
• resource state fetched from the API against the latest event you processed.

Events are an audit input, not the balance source of truth. If an event was missed or delivered out of order, rebuild current state from the list and get endpoints.

Recovery checks

Run periodic recovery jobs that:

• revisit recently changed clients and receivables;
• compare stored event IDs to processed IDs;
• follow all list pages;
• preserve unfamiliar statuses for investigation; and
• alert on financial records that cannot be joined to a known client payment.

The current PNSL contract does not expose a separate statement resource. Use receivables, their transaction records, credit accounts, and your own ledger as the reconciliation set.