Kintsugi
Your invoices, customers, and items land in Kintsugi read-only. DualEntry stays the source of record, and nothing is written back to your ledger.
Overview
Sales tax exposure hides in details you have already recorded: which customer, which address, which product, which legal entity. That data sits in your ledger. The tool that watches it sits somewhere else, and closing the gap by hand means exporting invoices and customer lists on a schedule nobody enjoys keeping.
This connection replaces that with a one-way import. You create a DualEntry API key carrying the Admin role under Settings > Developer Access, then paste it into Kintsugi under Data Sources > Browse Integration, pick Production or Development, and either leave the Companies field at its default to bring in every company in your DualEntry account or scope it to the entities you want. Kintsugi runs an initial import and continues pulling on an ongoing basis. While the first import runs the integration shows a status of Syncing, and it changes to Read-Only when the mirror is in place.
The flow runs in one direction only. DualEntry is the source of record for transactions, customers, and items; Kintsugi holds a read-only copy and uses it for sales tax exposure monitoring and reporting. Nothing Kintsugi calculates or stores flows back into your DualEntry ledger, so master data in each system is maintained independently and any correction you want reflected on the books is made in DualEntry.
There is no managed third-party connector platform in the middle. The DualEntry connector lives in Kintsugi's own Data Sources catalog and is authorized by a single DualEntry Admin API key that you generate and paste in; credentials are never exchanged in the other direction. Kintsugi's tax engine is not yet available through this connection, so it does not calculate sales tax and post it onto your DualEntry transactions.
Transactions (invoices)
Customers
Customer addresses
Items (products)
Product categories and subcategories
Companies (legal entities)
Data synced
The integration syncs the following data types:
- Your DualEntry invoices and transactions import into Kintsugi and appear on the Kintsugi dashboard, where they are used for sales tax exposure monitoring and reporting
- The initial import brings existing transactions across, and the connection continues pulling transactions on an ongoing basis after that first run completes
- Transactions are held read-only inside Kintsugi, so nothing Kintsugi derives from them is posted back onto the DualEntry transaction or its tax lines
- Kintsugi's tax engine is not yet available through this connection, so Kintsugi does not calculate sales tax and write it onto your DualEntry transactions
- Once the integration status changes from Syncing to Read-Only, verify on the Kintsugi dashboard that your DualEntry invoices and transactions have all arrived
- Your DualEntry customer list imports into Kintsugi, where it is used for the customer list and for address validation
- Kintsugi validates addresses after import and flags any that are invalid or incomplete, suggesting a corrected address for each flagged record
- Flagged addresses can be resolved two ways: accept all suggested corrections at once with a bulk update, or review and confirm each correction separately
- Because the address determines the taxing jurisdiction Kintsugi applies, completing customer addresses in DualEntry before the import reduces the cleanup work afterwards
- Corrections accepted in Kintsugi do not reach your ledger, so the docs direct you to complete the address in DualEntry as well
- Your DualEntry items import into Kintsugi as products and are used for product categorization that drives taxability
- The initial import covers your existing item list, and items continue to flow into Kintsugi on an ongoing basis after that
- Products are not all taxed at the same rate, so the docs call out accurate categorization on imported items as the thing that makes monitoring correct
- After the sync finishes, review the imported products in Kintsugi and check that a category and subcategory are assigned to each one
- Item records remain read-only in Kintsugi; item master data in each system is maintained independently
- Kintsugi Intelligence, the AI engine inside Kintsugi, automatically identifies a category and subcategory for each product it imports from DualEntry
- Taxability depends on the assigned category, so every suggestion is presented for your review rather than applied silently
- You can approve suggestions individually, reviewing one product at a time, or bulk approve all suggested categories at once from the dashboard
- Products left unapproved show as pending in Kintsugi until you confirm their categories individually or in bulk
- Categories and subcategories live in Kintsugi only and are never written onto the item record in DualEntry
- By default Kintsugi imports every company in your DualEntry account, so scope the Companies field during setup if you only want specific legal entities
- The companies you tax have to exist in DualEntry before the import runs, since Kintsugi pulls the entity list from your account rather than creating it
- The Companies field sits in the same connection modal as Environment and API Key, and is set once when you first connect the data source
- Because a single Admin API key authorizes the whole import, entity scope is controlled by that Companies setting rather than by the key itself
- You generate an API key with the Admin role in DualEntry under Settings > Developer Access, then paste it into Kintsugi under Data Sources > Browse Integration alongside an Environment of Production or Development
- DualEntry displays the key only once at creation, so if it is lost before you paste it into Kintsugi you generate a replacement rather than retrieving the original
- A key with a role below Admin cannot complete the import, and no credential is exchanged in the other direction
- In Data Sources > Manage Integrations the connection reads Syncing while the initial import runs and Read-Only once it finishes, which confirms Kintsugi is mirroring DualEntry data in read-only mode
- If the connection fails after you choose Save, the documented causes are an incorrect API key or the wrong Environment selection, and the fix is to verify both and reconnect from Browse Integration
Key Features
- Read-only by design
Records move from DualEntry into Kintsugi and never the other way. Kintsugi does not write to your ledger, so an import can never alter a posted transaction or a master record. - Invoices imported for exposure monitoring
Your DualEntry invoices and transactions land on the Kintsugi dashboard, where Kintsugi uses them for sales tax exposure monitoring and reporting. - Customer addresses validated after import
Kintsugi checks imported customer addresses, flags any that are invalid or incomplete, and suggests a correction. Accept them in bulk or review them one at a time. - Product taxability categorization
Kintsugi Intelligence, the AI engine inside Kintsugi, assigns a category and subcategory to every item it imports. You approve the suggestions individually or all at once from the dashboard. - Every company, or only the ones you choose
By default Kintsugi imports every company in your DualEntry account. Scope the Companies field during setup to limit the connection to specific legal entities. - Initial import, then ongoing
The first sync brings your existing transactions, customers, and items across. After that the connection keeps pulling on an ongoing basis with no export step on your side. - Status you can check
Data Sources > Manage Integrations shows Syncing while the initial import runs and Read-Only once it finishes, which is your confirmation that Kintsugi is mirroring DualEntry correctly. - One Admin API key, one direction
The connection is authorized by a single DualEntry API key with the Admin role, generated in Settings > Developer Access and shown only once at creation. A key with a lesser role cannot complete the import, and no Kintsugi credential is ever stored in DualEntry.
FAQ
There is no managed connector platform sitting between the two systems. The DualEntry connector lives in Kintsugi's own Data Sources catalog, and you authorize it by generating a DualEntry API key with the Admin role under Settings > Developer Access and pasting it into Kintsugi. Credentials are never exchanged in the other direction, so DualEntry holds no Kintsugi login.
Kintsugi is of course a separate vendor, and the copy of your data it imports is held and processed in Kintsugi. What that copy is used for is sales tax exposure monitoring and reporting inside Kintsugi.
Kintsugi monitors sales tax exposure from your transaction, customer, and item data. Without a connection, getting that data over means exporting invoices and customer lists out of your ledger and keeping the copies current by hand.
This integration removes the export step. After an initial import, your DualEntry transactions, customers, and items keep flowing into Kintsugi on an ongoing basis, and Kintsugi works from that data to monitor exposure and prepare reporting. Your ledger is untouched by the process.
No. The sync is one-way and read-only: records move from DualEntry into Kintsugi and nothing moves back. DualEntry is the source of record, and Kintsugi holds a copy for monitoring.
That means master data in each system is maintained independently. If Kintsugi suggests a corrected customer address or a product category, accepting it updates the record in Kintsugi; to change what your books say, you edit the record in DualEntry.
Not through this connection. The documented limitation is that the tax engine is not yet available, so the integration supports read-only data sync and reporting only. Kintsugi does not calculate sales tax and write it onto your DualEntry transactions.
Anything Kintsugi determines from the imported data stays in Kintsugi. Amounts posted in your DualEntry ledger are unchanged by the connection.
Each of the three record types follows the same pattern: an initial import, then ongoing. The first import can take a while depending on how much data you have, and while it runs the integration shows a status of Syncing in Data Sources > Manage Integrations.
When the status changes to Read-Only, the initial import is finished and Kintsugi is mirroring your DualEntry data. The documentation does not state a fixed interval for the ongoing syncs that follow.
The documented failure modes are narrow. A status that stays on Syncing usually just means a large volume is still importing, and it moves to Read-Only when it finishes. A connection that fails after you choose Save points to an incorrect API key or the wrong Environment selection, so verify both and reconnect from Data Sources > Browse Integration. If you lost the API key before pasting it, generate a new one in DualEntry under Settings > Developer Access, since the key is shown only once at creation.
Records that arrive but need attention are surfaced as pending tasks rather than errors: products awaiting category confirmation, and customer addresses flagged as invalid or incomplete with a suggested correction. Both are resolved individually or in bulk from the Kintsugi dashboard.
.avif)