-
Notifications
You must be signed in to change notification settings - Fork 41
Missing Expenses and Payables updates #1739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📝 [vale] reported by reviewdog 🐶 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📝 [vale] reported by reviewdog 🐶 |
||
|
|
||
| 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. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📝 [vale] reported by reviewdog 🐶 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📝 [vale] reported by reviewdog 🐶 |
||
|
|
||
| ## Invoices | ||
|
|
||
| Writing negative invoices to Sage Intacct is not supported; you can write a Credit Note to achieve this functionality. | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📝 [vale] reported by reviewdog 🐶 |
||
|
|
||
| ## 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 | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 [vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('be posted').