Skip to content
All connectors
Sage Business Cloud Accounting logo

Sage Business Cloud Accounting

Accounting, billing & payments

Keep Sage Business Cloud Accounting in step with your orders, invoices and payments without re-keying, with the right person approving what changes.

18 ways to read, 9 ways to write, each write switched on by you.

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Sage Business Cloud Accounting with Nexra

Connected, approved, proven.

The things teams do most with Sage Business Cloud Accounting, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Record contact paymentcontact_payments.createApproval by rule
  • Create contactcontacts.createApproval by rule
  • List bank accountsbank_accounts.listRead

Example flow

  1. Flutterwave · Read settlementssettlements.listDone
  2. Sage Business Cloud Accounting · Create journaljournal_entries.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Sage Business Cloud Accounting.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Sage Business Cloud Accounting
  • Sage Business Cloud Accounting's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

For developers

Technical detail

Read and write Sage Accounting sales and purchase invoices, payments, products, services, ledgers, tax rates and quotes; read credit notes, journals and bank activity.

Sage API docs
Source actions
18
Destination actions
9
Data types
18

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

bank accounts1
  • List bank accountsSourceIncremental

    Bank, cash and card accounts with balance and ledger account.

bank transactions1
  • List other bank payments and receiptsSourceIncremental

    Money paid out of or received into bank accounts that is not an invoice payment (other payments and other receipts).

bank transfers1
  • List bank transfersSourceIncremental

    Transfers between the business's bank accounts.

contact payments2
  • Record contact paymentDestinationNot retried automaticallyApproval before production

    Records a customer receipt or vendor payment already made and allocates it to invoices. No money is moved.

  • List contact paymentsSourceIncremental

    Customer receipts and vendor payments with their invoice allocations.

contacts3
  • Create contactDestinationNot retried automaticallyApproval before production

    Creates a customer or supplier, for example a new buyer from a store or CRM, so invoices and payments can be raised against it.

  • List contactsSourceIncremental

    Customers and suppliers with references, balances, credit terms and main address.

  • Update contactDestinationProvider duplicate protectionApproval before production

    Updates supplied fields on a customer or supplier.

credit notes2
  • Create sales credit noteDestinationNot retried automaticallyApproval before production

    Creates a customer credit note with its lines (reconciliation: an over-invoiced or cancelled order). No refund is paid.

  • List sales credit notesSourceIncremental

    Customer credit notes with lines, status and unallocated amounts.

customer payments1
  • List customer receiptsSourceIncremental

    Customer receipts (contact payments of type CUSTOMER_RECEIPT) with their invoice allocations.

customers1
  • List CustomersSource

    List operation for Customers.

journal entries2
  • Create journalDestinationNot retried automaticallyApproval before production

    Records a balanced manual journal (reconciliation: a fee, a refund or a realised exchange difference). No money is moved.

  • List journalsSourceIncremental

    Manual journals with debit and credit lines.

ledger accounts1
  • List ledger accountsSourceIncremental

    Chart of accounts with nominal codes, types and default tax rates.

products3
  • Create productDestinationNot retried automaticallyApproval before production

    Creates a product with sales and purchase ledger accounts.

  • List productsSourceIncremental

    Stock and non-stock products with prices and ledger accounts.

  • Update productDestinationProvider duplicate protectionApproval before production

    Updates supplied fields on a product.

purchase invoices2
  • Create purchase invoiceDestinationNot retried automaticallyApproval before production

    Records a supplier invoice.

  • List purchase invoicesSourceIncremental

    Supplier invoices with lines, status and outstanding amounts.

sales invoices2
  • Create sales invoiceDestinationNot retried automaticallyApproval before production

    Creates a sales invoice for a customer contact.

  • List sales invoicesSourceIncremental

    Sales invoices with lines, status and outstanding amounts.

sales quotes1
  • List sales quotesSourceIncremental

    Sales quotes with status, expiry and lines.

services1
  • List servicesSourceIncremental

    Services with rates and ledger accounts.

tax rates1
  • List tax ratesSourceIncremental

    Tax rates with percentage and agency.

vendor credits1
  • List purchase credit notesSourceIncremental

    Supplier credit notes with lines, status and unallocated amounts.

vendor payments1
  • List vendor paymentsSourceIncremental

    Vendor payments (contact payments of type VENDOR_PAYMENT) with their invoice allocations.

Access and limits

Authentication
Sage OAuth 2.0 access token
Plans and access
Sage Accounting subscriptions in supported regions (UK, Ireland, Canada, US, France, Spain). Available fields and tax handling vary by region. The user who authorised the app must have access to the business.
Test environment
Developers can create trial businesses through the Sage developer self-service portal.
Rate limits
Per-business request quotas apply; HTTP 429 when exceeded and Nexra waits before retrying.
Pagination
page and items_per_page (up to 200); $next indicates another page.
Provider events
Sage Accounting does not offer general-purpose API webhooks. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Customer reads, OAuth authentication and pagination implemented.
  • Sage does not document idempotency keys for these endpoints; uncertain creates are not repeated automatically.
  • Contact payments are limited to customer receipts and vendor payments; refunds are not implemented.
  • Deletes, voids and invoice emailing are not implemented.
  • Bank transactions: bank_transactions.list returns other payments and receipts; customer receipts, vendor payments and bank transfers have their own reads. Sage's API has no bank statement or bank feed line endpoint.
  • Orders: Sage Accounting has no sales order or purchase order API (only quotes and estimates), so order reads are not available; sales_quotes.list covers quotes.
  • Journals can be filtered by updated or created time only; Sage documents no journal date range filter.
  • contacts.create and contacts.update send name, type, reference, tax number, currency, credit terms, notes and main address; contact people and email addresses are not written yet.

Developer reference

  1. Create the Sage credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Sage Business Cloud Accounting, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/sage-business-cloud-accounting and the Connections API.