Webhook integrations: finance work that starts when something happens

Most finance automation runs on a timer. The payout completed this morning, but matching starts tonight. The order came in before lunch, but the checks run tomorrow. In between, the books are quietly out of date, and anything that went wrong sits unnoticed until the next scheduled pass picks it up.

Webhooks remove the waiting. When something happens in your systems (a new order, a completed payout, an updated record) the event triggers Nance directly and the work starts then and there. It runs the other way too: when Nance finishes something (a booking made, an approval given) it notifies the systems that need to know. Every event is signed and verified before anything runs, and every triggered workflow is logged from event to outcome. Real-time, but still under your rules.

What Nance automates with Webhooks

Event-driven triggers

A webhook from any of your systems can start a Nance workflow. The work begins when something happens, not when a schedule decides it is time to look.

Order events

A new order lands in your ordering system and Nance prepares the trail behind it: references checked, documents expected, the administration ready before anyone asks.

Payout events

Your payment provider completes a payout and Nance starts matching it against the underlying transactions right away, instead of waiting for the next batch run.

Record updates

A supplier detail changes, a contract is renewed, a customer record moves: Nance picks up the event and checks whether the administration still agrees with it.

Outbound notifications

Nance calls your systems when finance work completes: a booking done, an approval given, a document attached. Your tools stay current without polling for changes.

Signed and logged

Every incoming webhook is signed and verified before anything runs, and every triggered workflow is logged from event to outcome.

Frequently asked questions

How are webhooks secured?

Every payload is signed, so Nance verifies that an event really came from your system before acting on it. Webhooks from Nance to your systems are signed the same way, so you can verify us too.

What if the same event arrives twice?

Nance deduplicates incoming events and checks the current state of the administration before acting, so a repeated webhook does not become a repeated booking.

Can an event trigger actions automatically?

An event can start a workflow, but the workflow still follows your rules. You decide which steps run straight through and which wait for approval, exactly as with every other trigger.

Why webhooks instead of scheduled runs?

Schedules mean work waits for the next run and exceptions surface late. With events, the work starts the moment something happens and your systems hear back the moment it is done.

Work starts on the event, not on the clock