What does Nance need from our API?

A way to authenticate plus documentation, or even a handful of example calls. REST with token authentication covers most systems. We help you map the endpoints to the finance workflows you want.

Can Nance change data in our systems?

Only if you grant write access, and only within your approval rules. You can keep a connection read-only and still get most of the value: verification, reconciliation and document retrieval.

Is this safe with internal systems?

Each connection uses its own scoped credentials, approval gates apply to every action, and every call is logged with its context and outcome. You decide how far a connection reaches.

When should we use this instead of a native integration?

Use native integrations where we offer them; they go deeper and are tuned for finance work. Custom API connections are for everything else: internal tools, niche software and systems we do not cover yet.

Nance + Custom APIs.

Connect anything

Your stack does not end where an integration list ends. Nance reads from any system with a REST API and, where you allow it, acts on it, under the same approvals and logging as everything else.

Book a demo See how she works

The systems that slow your finance team down are rarely the famous ones. It is the internal ordering system that holds the truth about what was delivered. The industry package that issues the invoices. The portal where the supporting documents live. None of them appear on any integration list, so their data moves by export, screenshot and copy-paste, and someone reconciles the differences by hand.

Nance does not need a ready-made connector to work with them. Anything with a REST API can be connected: Nance reads from it to reconcile, fetches documents, verifies entries against the source, and where you allow it, acts on it. Every connection runs on its own scoped credentials, every action passes your approval rules, and every call is logged with its context and outcome. Your finance agent reaches as far as your stack does, on your terms.

Why connect Nance to Custom APIs.

The connection and the colleague in one

She reads Custom APIs, applies your rules and does the actual finance work in your accounting system.

Nothing posts outside your rules

You decide what runs automatically and what waits for approval. Every action logged, with the why attached.

One agent across the stack

Payments, commerce, CRM, spend and inboxes: one set of rules and a full audit trail between them.

Up and running in three steps.

Connect
Through the official Custom APIs API, with scoped access. Nothing to install and nothing to migrate.
Set the rules
What she books on her own, what waits for you, who approves. Start anything as a Test Run: a read-only preview first.
She works daily
What arrives in Custom APIs is read, matched and booked in your accounting system. Exceptions come to you with context.

What Nance automates with Custom APIs

Internal systems

The ordering system your team built years ago, the data warehouse, the homegrown CRM. If it exposes an API, Nance can pull from it and fold it into the same workflows as your accounting system.

Niche and legacy software

The industry-specific package nobody integrates with usually still has an API somewhere. That is enough for Nance to read from it, verify against it and stop retyping its data by hand.

Reconciliation data

Nance pulls orders, payouts and reference data from your systems to match against bank lines and invoices, so reconciliation does not stop at the edge of your accounting package.

Document retrieval

Invoices and supporting documents that live behind a login in your own systems get fetched and attached where they belong, instead of waiting for someone to export them.

Cross-system verification

Before an entry posts or a payment is proposed, Nance checks the source system: does the order exist, was the delivery confirmed, does the amount match what was agreed.

Scoped actions

Where you allow it, Nance acts on your systems: update a status, trigger a process, write a reference back. Every action runs on scoped credentials and under your approval rules.

Access and security

No bank connection, no bank credentials, ever
Her own user account with scoped permissions
Every action logged, visible and attributable
Test Run: read-only preview before anything changes
Hosted on Google Cloud in the EU
Your data never trains AI models

Frequently asked questions

Connect Custom APIs to Exact Online, Twinfield, Moneybird, Xero and QuickBooks

Most Custom APIs connectors are data pipes: they copy fields on a schedule and stop there. Nance is the connection and the colleague in one. It reads Custom APIs, applies your rules and does the actual finance work in your accounting package, with approvals where you want them and every action logged.

Exact Online

Book, reconcile and close inside your Exact Online administration

Twinfield

Automated processing and period checks across Twinfield administrations

Moneybird

Keep your Moneybird books current and VAT-ready, automatically

Xero

Automate invoice processing and reconciliation in Xero

QuickBooks

Bills coded, bank lines matched and debtors chased inside QuickBooks Online

Security is part of the job.

Nance works inside your financial systems, so we treat protecting them as core product work. The live details are public in our trust center.

Encrypted everywhere

AES-256 at rest, TLS in transit.

GDPR compliant

a standard DPA with every plan.

ISO 27001

certification in finalization.

Hosted in the EU

on Google Cloud, by default for everyone.

Never trains AI models

your data stays yours alone.

Payments stay at your bank

Nance prepares the batch, you release it.

Open the trust center →More on security →

✓ Booked 42 purchase invoices✓ Matched €18,430.00 in bank transactions✓ Flagged 1 duplicate from Coolblue✓ Prepared Thursday's payment run✓ Chased 6 overdue invoices✓ Held 1 changed IBAN for review✓ Refreshed the cash dashboard✓ Closed February, clean

✓ Matched €18,430.00 in bank transactions✓ Flagged 1 duplicate from Coolblue✓ Prepared Thursday's payment run✓ Chased 6 overdue invoices✓ Held 1 changed IBAN for review✓ Refreshed the cash dashboard✓ Closed February, clean✓ Booked 42 purchase invoices

✓ Flagged 1 duplicate from Coolblue✓ Prepared Thursday's payment run✓ Chased 6 overdue invoices✓ Held 1 changed IBAN for review✓ Refreshed the cash dashboard✓ Closed February, clean✓ Booked 42 purchase invoices✓ Matched €18,430.00 in bank transactions

✓ Prepared Thursday's payment run✓ Chased 6 overdue invoices✓ Held 1 changed IBAN for review✓ Refreshed the cash dashboard✓ Closed February, clean✓ Booked 42 purchase invoices✓ Matched €18,430.00 in bank transactions✓ Flagged 1 duplicate from Coolblue

✓ Chased 6 overdue invoices✓ Held 1 changed IBAN for review✓ Refreshed the cash dashboard✓ Closed February, clean✓ Booked 42 purchase invoices✓ Matched €18,430.00 in bank transactions✓ Flagged 1 duplicate from Coolblue✓ Prepared Thursday's payment run

✓ Held 1 changed IBAN for review✓ Refreshed the cash dashboard✓ Closed February, clean✓ Booked 42 purchase invoices✓ Matched €18,430.00 in bank transactions✓ Flagged 1 duplicate from Coolblue✓ Prepared Thursday's payment run✓ Chased 6 overdue invoices

✓ Refreshed the cash dashboard✓ Closed February, clean✓ Booked 42 purchase invoices✓ Matched €18,430.00 in bank transactions✓ Flagged 1 duplicate from Coolblue✓ Prepared Thursday's payment run✓ Chased 6 overdue invoices✓ Held 1 changed IBAN for review

✓ Closed February, clean✓ Booked 42 purchase invoices✓ Matched €18,430.00 in bank transactions✓ Flagged 1 duplicate from Coolblue✓ Prepared Thursday's payment run✓ Chased 6 overdue invoices✓ Held 1 changed IBAN for review✓ Refreshed the cash dashboard

Hire Nance.

Connected to Custom APIs in an afternoon, and we walk you through it.

Book a demo See pricing