Merge pull request #1739 from codatio/fix/missing-updates

Missing Expenses and Payables updates

Author: pzaichkina

blog/251003-deprecation-of-integrations.md

@@ -11,6 +11,12 @@ To streamline our platform and enable us to focus on our key products, Codat is
 
 ## Q4 2025 deprecations
 
+:::info 23 December, 2025: Update
+
+The deprecation of these integrations has now been completed as scheduled. The **Lightspeed K** integration will be deprecated on **January 10, 2026** instead.
+
+:::
+
 The following integrations will be **fully deprecated and permanently removed** from the Codat platform on **October 31, 2025**:
 
 | Commerce Integrations | Banking Integrations | Accounting Integrations |

docs/expenses/overview.md

@@ -149,7 +149,7 @@ When creating an expense transaction, allow your SMB customer to save a copy of
 | Oracle NetSuite    | ✔️                    | ✔️                                |                       |                         |
 | QuickBooks Desktop | ✔️                    | ✔️                                | ✔️                    | ✔️                      |
 | QuickBooks Online  | ✔️                    | ✔️                                | ✔️                    | ✔️                      |
-| Sage Intacct       | ✔️ (credit card only) |                                   |                       |                         |
+| Sage Intacct       | ✔️                    | ✔️                                |                       |                         |
 | Xero               | ✔️                    |                                   | ✔️                    | ✔️                      |
 | Zoho Books         | ✔️                    | ✔️                                |                       |                         |
 

docs/get-started/libraries.md

@@ -13,8 +13,6 @@ Codat offers official SDK client libraries for different programming languages,
 
 <ClientLibraries />
 
-Looking for a language that's not here? [Request support for a new language](https://forms.gle/jEWjV1EDhiB5KEGP9).
-
 ### Library versions
 
 Codat's client library version policy uses [semantic versioning](https://semver.org/spec/v2.0.0.html). For example, a library version 4.2.0 defines the _major_ version as 4, _minor_ as 2, and the _patch_ as 0.

docs/integrations/accounting/sage-intacct/sage-intacct-integration-reference.md

@@ -54,6 +54,12 @@ Direct Incomes are mapped from the [Other Receipts](https://developer.intacct.co
 
 When writing Direct Incomes to Sage Intacct, the required `otherreceipt.payee` field is populated with the value of `directIncomes.reference`. The `otherreceipt.payee` field is not associated with a customer or contact.
 
+## Expenses
+
+Expense transactions can't be posted directly from debit accounts to Sage Intacct. Instead, all card-based expenses (this includes credit, debit, and prepaid cards) are posted using the `Credit Card Charge` object. 
+
+If debit card expenses need to be synced, the customer can set the account type to `Debit` for this object. The resulting transactions are then correctly posted to the general ledger accounts, and the account is reflected as a debit account in the Sage Intacct user interface.
+
 ## Invoices
 
 Writing negative invoices to Sage Intacct is not supported; you can write a Credit Note to achieve this functionality.

docs/integrations/accounting/xero/xero-faq.md

@@ -213,4 +213,4 @@ For example:
 ### For certain bills and invoices, why does the sum of the line items not add up to the exact Total Amount?
 
 In Xero, it is possible for an end user to overwrite the total of an AR/AP Invoice to within 0.10 decimal places of the total of the line items. The adjustment is attributed to a rounding account, but left off from being a line item on the bill itself.
-Codat does not throw an error in these cases, but instead logs a warning. These warnings are visible via the [read.completed webhook payloads](https://docs.codat.io/using-the-api/webhooks/event-types), or the [Get Validation Results endpoint](platform-api#/operations/get-read-validation-results)
+Codat does not throw an error in these cases, but instead logs a warning. These warnings are visible via the [read.completed webhook payloads](https://docs.codat.io/using-the-api/webhooks/event-types), or the [Get Validation Results endpoint](/platform-api#/operations/get-read-validation-results)

docs/payables/get-started.md

@@ -25,17 +25,17 @@ Once you decide to build with Bill Pay, you need to configure Codat accordingly.
 
 1. Open the <a href="https://app.codat.io" target="_blank">Codat Portal</a> and sign in.
 2. Click on **Settings > Organizational settings > Products**.
-3. In the list of products, find the relevant version of _Bill Pay_ (async or sync) and click **Enable**. Then, follow the on-screen prompt.
+3. In the list of products, find _Bill Pay_ and click **Enable**. Then, follow the on-screen prompt.
 
 ## Configure Bill Pay
 
 ### Data types
 
 In the <a href="https://app.codat.io" target="_blank">Codat Portal</a>, navigate to **Settings > Integrations > Data types**. Enable the [data types](/core-concepts/data-type-settings#override-the-default-sync-settings) required for Bill Pay and set them to `Fetch on first link`:
 
-| Data source | Bill Pay (async)                                                                                                                                                                              | Bill Pay (sync)                                                                                                                   |
-| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| Accounting  | `bankAccounts`<br/> `bills`<br/> `billCreditNotes`<br/> `billPayments`<br/> `chartOfAccounts`<br/> `company`<br/> `paymentMethods`<br/> `suppliers`<br/> `taxRates`<br/> `trackingCategories` | `bankAccounts`<br/> `bills`<br/> `billPayments`<br/> `chartOfAccounts`<br/> `company`<br/> `paymentMethods`<br/> `suppliers`<br/> |
+| Data source | Data types                                                                                               		                  |
+| ----------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| Accounting  | `bankAccounts`<br/> `bills`<br/> `billPayments`<br/> `chartOfAccounts`<br/> `company`<br/> `paymentMethods`<br/> `suppliers`<br/> |
 
 Configure the solution to refresh data when you need it by [setting a synchronization frequency](/core-concepts/data-type-settings#choose-a-synchronization-frequency) on the same screen. We recommend setting it to a daily or a monthly sync.
 
@@ -45,12 +45,6 @@ In the <a href="https://app.codat.io" target="_blank">Codat Portal</a>, navigate
 
 You can also view detailed configuration instructions by clicking on the relevant tile:
 
-#### Integrations supported by async Bill Pay
-
-<IntegrationsList filter={integrationsFilterBillPayAsync} />
-
-#### Integrations supported by sync Bill Pay
-
 <IntegrationsList filter={integrationsFilterBillPaySync} />
 
 ### Authorization flow

docs/payables/overview.mdx

@@ -116,57 +116,12 @@ Pay process consists of three key steps:
    to Codat. We will reflect this transaction in your customer's accounting
    software and reconcile it against the original bill, marking it as paid.
 
-We designed two versions of our solution so that you can choose the one that
-solves the specific needs of your accounting automation use case:
-
-<ul className="card-container col-2">
-<li className="card">
-    <div className="header">
-        <img src="/img/wp-icons/clock-countdown.svg"
-            className="mini-icon"/>
-        <h3><a href="https://docs.codat.io/payables/async/suppliers">Asynchronous Bill Pay</a></h3>
-    </div>
-    <p>
-      Bill Pay's async version handles even the most complex accounts payable workflows with ease, including scenarios that manage credit notes, refunds, partial payments, and bulk payments.
-    </p>
-</li>
-
-<li className="card">
-  <div className="header">
-    <img src="/img/wp-icons/clock-clockwise.svg" className="mini-icon" />
-    <h3>
-      <a href="https://docs.codat.io/payables/sync/suppliers">
-        Synchronous Bill Pay
-      </a>
-    </h3>
-  </div>
-  <p>
-    Sync Bill Pay is designed to integrate a bill pay flow into your app as
-    quickly as possible, focusing on simplicity and efficiency of its endpoints.
-    This version offers real-time updates with your SMBs' accounting systems.
-  </p>
-</li>
-
-</ul>
+Bill Pay is designed to integrate a bill pay flow into your app as quickly as possible, focusing on simplicity and efficiency of its endpoints and real-time updates with your SMBs' accounting systems.
 
 ## Supported integrations
 
-<Tabs>
-
-<TabItem value="async" label="Asynchronous Bill Pay">
-
-<IntegrationsList filter={integrationsFilterBillPayAsync} />
-
-</TabItem>
-
-<TabItem value="sync" label="Synchronous Bill Pay">
-
 <IntegrationsList filter={integrationsFilterBillPaySync} />
 
-</TabItem>
-
-</Tabs>
-
 ## Build with client libraries
 
 Use our [comprehensive SDKs](/get-started/libraries) to kick-start and simplify

docs/payables/sync/pay-bill.md

@@ -10,7 +10,7 @@ description: "Record and reconcile bill payments in the SMB's accounting softwar
 Finally, your SMB customer will make a payment from your application, which you should then record and reconcile back to the SMB's accounting software. A **bill payment** represents an allocation of money within any of your customer's accounts payable (AP) accounts.
 
 :::tip Bill type coverage
-Our **sync Bill Pay** solution focuses on providing a fast implementation experience and streamlined recording of payments. As a result, it supports payments of **single bills only**. If you want to cover more bill types, review our [async Bill Pay solution](/payables/async/payments).
+Our **sync Bill Pay** solution focuses on providing a fast implementation experience and streamlined recording of payments. As a result, it supports payments of **single bills only**.
 :::
 
 ## Manage payment accounts

docs/using-the-api/overview.md

@@ -15,7 +15,7 @@ We've packaged up Codat's functionality mainly by _solution_, with our _Platform
 | **[Bank Feeds](/bank-feeds-api)**                                                                  | Set up bank feeds from accounts in your application to supported accounting software.                                            |
 | **[Lending](/lending-api)**                                                                        | Make credit decisions backed by enhanced financials, metrics, reports, and data integrity features.                              |
 | **[Expenses](/sync-for-expenses-api)**                                                             | Streamline expense reconciliation from the corporate card and expense management systems to your customers' accounting software. |
-| **[Bill Pay (async)](/sync-for-payables-api)**, **[Bill Pay (sync)](/sync-for-payables-v2-api#/)** | Make it easier for your customers to manage and pay suppliers from a single interface.                                           |
+| **[Bill Pay](/sync-for-payables-v2-api#/)**                                                        | Make it easier for your customers to manage and pay suppliers from a single interface.                                           |
 
 Explore the underlying [OpenAPI Spec](https://github.com/codatio/oas).
 

nav.config.js

@@ -30,13 +30,9 @@ module.exports = {
           label: "Bank Feeds",
           hr: true,
         },
-        {
-          href: "/sync-for-payables-api",
-          label: "Bill Pay (async)",
-        },
         {
           href: "/sync-for-payables-v2-api",
-          label: "Bill Pay (sync)",
+          label: "Bill Pay",
         },
         {
           href: "/sync-for-expenses-api",