Your user authorizes your application to access their accounting service (e.g., QuickBooks Online, NetSuite) via an OAuth or similar authorization flow through Merge Link.

The following steps will cover the business logic you will need to configure in your backend to interact with Merge’s Unified API.

“Settings” data refers to all information related to customers, accounts, items, and tracking categories. To do this, we will access four endpoints:

• Sync your customer’s chart of accounts by using the GET /accounts endpoint.
• You can use the classification and parent_account fields to compile account types and hierarchy!
• Follow the steps outlined in the Sync Customers or Suppliers” use case to sync your customers in your system with the third party.
• If your customer has classes, locations, or departments configured, you can retrieve them from the accounting platform with GET /Tracking Categories.
• Utilize the GET /items endpoint to pull in your customer’s products, goods, and services.

Retrieve all invoices for all customers:

• Use the GET /Invoices endpoint to access all invoices, and set the type query param = ACCOUNTS_RECEIVABLE to filter to only AR invoices.
• Look at the balance and status fields to find invoices that are not fully paid.

Based on the reconciliation process that occurs within your platform, you’ll programmatically create payments and/or invoices.

• If an Invoice does not exist for a receipt of money, create an Invoice using the POST /invoice endpoint and corresponding Payment using the POST /payment endpoint.
• If an Invoice is not yet paid, create a Payment against the Invoice using the POST /payment endpoint.
• If you need to update an Invoice or Payment in the accounting platform, you can use PATCH /invoice or PATCH /payment endpoints.