Nudge: integration overview
Nudge keeps Alderstone in step with your ERP or GL system: it pulls debtors, invoices, and payments in, and pushes dispatched invoices and applied payments back out.
What the integration does
Data moves in both directions over the same connection:
| Direction | Operations | When |
|---|---|---|
| Inbound (ERP → Alderstone) | Debtors/contacts, ACCREC invoices, payments | Initial connect, manual Sync now, nightly scheduled sync |
| Outbound (Alderstone → ERP) | Invoice dispatch, cash application payments | Immediately when an invoice is dispatched or a cash application is approved |
The Sync & push flows page details each trigger, pagination, incremental sync, and idempotency behaviour.
Choosing a transport
Configure one active transport per company in Settings → ERP connection:
- Native: built-in ERP integration using OAuth or API credentials, depending on the ERP. No development work needed.
- REST: Alderstone calls your middleware, which implements the Nudge REST API. Works with any GL/AR system.
Not sure which fits? See Choose your integration path.
Setting up a REST connection
- Implement
POST /healthon your middleware; this is what the connection test calls on save. - In Settings → ERP connection, select REST, enter your middleware's base URL (no trailing slash), and click Generate API key.
- Store the
ask_…key in your middleware and validate it on every request. See Authentication. - Save, then run Sync now (or wait for the nightly sync) to pull the first full import.
Implement the three */list endpoints first so sync works, then add invoices/push and payments/push for outbound. The Quickstart covers the full build path.
Next steps
- REST API reference: endpoint with request/response examples
- Sync & push flows: triggers, pagination, and edge cases
- Troubleshooting: common fixes