Skip to main content
Business & GrowthAccounting Software31 lines

Integrate Invoice Ninja and Verify Payment Reconciliation

Map clients, invoices and payments in Invoice Ninja and verify totals, replay behavior and status using an owned test account.

Quick Summary9 lines
Record the Invoice Ninja version, company or tenant, API host, and authorized test account. Inspect the current API reference for clients, invoices and payments. List the inputs the accounting workflow needs, including currency, tax treatment, invoice date, due date, and contact mapping. Use synthetic clients and charges. Avoid using the provider's sending or payment steps until they are independently approved for the test environment.

## Key Points

- [Invoice Ninja invoice API guide](https://invoiceninja.github.io/docs/developer-guide/api/invoices)
- [Invoice Ninja API reference](https://invoiceninja.github.io/docs/api-reference/invoice-ninja-api-reference)
- [Invoice Ninja list clients](https://invoiceninja.github.io/docs/api-reference/get-clients)
skilldb get accounting-software-skills/invoice-ninjaFull skill: 31 lines
Paste into your CLAUDE.md or agent config

Integrate Invoice Ninja and Verify Payment Reconciliation

Model records before creating them

Record the Invoice Ninja version, company or tenant, API host, and authorized test account. Inspect the current API reference for clients, invoices and payments. List the inputs the accounting workflow needs, including currency, tax treatment, invoice date, due date, and contact mapping. Use synthetic clients and charges. Avoid using the provider's sending or payment steps until they are independently approved for the test environment.

Store an external invoice identity linked to the source order and the provider record. Map clients using stable identifiers instead of assuming names are unique. Define which system owns invoice number, tax classification, delivery state, and outstanding balance. Keep invoice creation and invoice sending as separate actions, since a newly created record need not have been delivered. Review required fields and default behavior against the installed version.

Verify totals and lifecycle

Create a small fixture invoice with two line items. Independently calculate the expected subtotal, tax and gross amount under the company's rounding rules. Read the saved invoice back through the API and compare values and currency. An accepted request or a displayed total alone cannot establish the invoice matches accounting policy. Record the mapping and only then exercise status transitions allowed for the test.

Register a partial payment using the approved test method. Reconcile the invoice total, amount received and amount still outstanding. Check that the payment belongs to the intended customer and invoice. Test a duplicate event or replay using the same external identity. If a write times out, read by the known identifier or reconcile the authorized records before another create. Handle any ambiguous result without issuing another customer notice or receipt.

Document failure and recoverability

Test an invalid customer mapping, wrong currency, and duplicate payment. Confirm the integration reports useful errors without logging invoice details or API credentials. Check whether partial work can be retried safely and ensure the source order and provider records remain linked. Use a restricted credential appropriate to the allowed test operations.

Record API and tenant identifiers, fixture totals, lifecycle states and reconciliation outcome. Keep evidence that identifies which test calls were read-only and which created synthetic records. Separate a successful integration test from authorization to deliver a real invoice or accept live payment.

References

Install this skill directly: skilldb add accounting-software-skills

Get CLI access →

Related Skills