Accounting & integrations

AppBill prepares operational spend for your ledger. Start with a reviewed CSV export, then add an integration when the mapping is stable and your team can reconcile the result.

Map your accounting fields

Match each AppBill category to one ledger account and each department to the corresponding dimension. Vendor, transaction date, amount, currency, tax, receipt, and business purpose travel with the record when the destination supports them.

Export a reviewed CSV

1. Open the export queue and filter to the posting period.
2. Resolve required-field warnings and duplicate flags.
3. Select the destination template and lock the batch.
4. Download the CSV and import it using your accounting platform’s normal controls.
5. Reconcile the batch total and record the export ID in your close checklist.

Use the API for a custom handoff

Scale workspaces can request API credentials for approved, locked batches. Keep credentials on the server, use least-privilege scopes, and verify webhook signatures before processing an event. Never place a secret key in browser code.

The example below requests one export batch. Replace the URL and token with values from your workspace agreement.

Copycurl --request GET \
  --url https://api.app-bill.us.com/v1/export-batches/batch_01JXYZ \
  --header "Authorization: Bearer $APPBILL_API_TOKEN" \
  --header "Accept: application/json"

Handle webhooks safely

Respond quickly, process asynchronously, and make the handler idempotent. Store the event ID so a repeated delivery does not create a duplicate journal entry. If signature verification fails, reject the request and investigate rather than accepting the payload “just once.”

Reconcile before you automate

For the first three close cycles, compare transaction count, net amount, tax, currency, and ledger period against the export summary. Automation should remove retyping, not remove review.