Skip to main content

AI Transactions

Use AI to post complex, data-entry heavy, and repetitive transactions straight from Double to your ledger.

AI Transactions is the fastest way to post complex or repetitive entries in Double - like payment processor exports, loan docs, payroll journals, or HUD/ALTA settlement statements - using an agentic AI workflow that learns your preferences over time.

It works across journal entries, bills, expenses, invoices, deposits, sales receipts, vendor credits and credit card credits, and a single source file can produce multiple transactions in one go. It's also a great way to delegate detail-heavy postings to junior staff: build (or generate) a reusable skill once, verify it, and let the agent reapply it the next time a similar document comes in.

Video Overview


What's new

  • Works for any transaction type - journal entries, bills, expenses, invoices, deposits, sales receipts, vendor credits and credit card credits (checks coming soon). Pick the transaction type you want to create at the start of the flow.

  • Multiple transactions from a single file - upload one document that contains several entries (e.g., a multi-line spreadsheet of JEs, or a PDF that bundles several bills) and Double can create and post all of them together.

  • AI Composer - a new, more intuitive entry point for kicking off an AI-posted transaction.

  • Agent-driven clarifying questions - the agent reads the document, thinks through how to map it, and asks you targeted questions (e.g., when the transaction should be posted) instead of forcing you to anticipate everything up front.

  • Reusable Skills (replaces saved prompts) - your selections can be saved as a skill that captures your preferences and updates client-specific memory for better context going forward.

  • Skill Manager - one place to open, edit, view, and apply your skills across clients.

  • Smart skill updates - when your selections diverge from an existing skill, the agent will ask if you want to update that skill rather than create a new one.


How to Post a Transaction Using AI

You can start an AI-posted transaction from two places: the Client Uploads inbox (best for documents you want to triage in batches, and required for posting multiple transactions from a single file) or the Quick Add menu on your client's close page (best for one-off, ad hoc transactions).

Start from Client Uploads

  • Go to the Client Uploads section from your client's close page

  • Add your document

    • Click Add a file and upload the relevant document (e.g., a loan statement, processor export, settlement statement, or a multi-bill PDF), or

    • Forward your document via your client's receipts e-mail address

  • Double will automatically scan the file

  • Once the file is scanned, click the filename to open it

  • Select the transaction type you'd like to create (Journal Entry, Bill, Expense, etc.)

Start from the Quick Add menu

You can also start an AI-posted transaction directly from your client's close page without sending the document through Client Uploads first:

  • Click Add in the top right of your client's close page to open the Quick Add menu

  • Select a transaction type

  • Upload your document

  • Begin chatting with the AI in the AI Composer

πŸ’‘ Posting multiple transactions from a single file is not supported via Quick Add - use the Client Uploads path for those.

Click into the AI Composer

The AI Composer is the new home base for setting up an AI-posted transaction. From here, you have a few options for getting started:

  • Start from an existing prompt or skill you've already created - great for recurring transactions.

  • Reference a similar transaction you've posted in the past so the agent can model the new one after it.

  • Send your own instructions to the agent, or simply type free text describing how the transaction should be mapped (which data to reference and how the numbers should be mapped to accounts, classes, locations, vendors, and customers).

Answer the agent's clarifying questions

After you send instructions, the agent will start thinking, reference the document, and ask clarifying questions as it goes - for example, recognizing the transaction type and asking when the transaction should be posted.

Your answers are used immediately for this transaction, can be saved to a reusable skill, and update client-specific memory so the agent has better context next time.

Review and post

Review the generated line items carefully:

  • Accounts

  • Vendors or customers

  • Amounts

  • Classes (if used)

  • Locations (if used)

  • Description

If you need to make changes:

  • Reply to the agent until it gets it right - this is recommended, so you can save and reuse a more accurate skill.

  • Directly edit the transaction.

If everything looks good:

  • Click the thumbs up to approve - this provides us with feedback and helps our AI get smarter.

  • Click Post (or Post all, when there are multiple transactions) to sync to your ledger.


Posting multiple transactions from a single file

Some files naturally contain more than one transaction - a multi-line journal entry spreadsheet that spans dates and customers, or a single PDF that bundles several bills. AI Transactions handles both, and you can also add transactions manually for ad hoc cases.

AI-generated (automatic)

  • When the AI processes a file containing multiple distinct transactions, it creates a transaction for each one based on your clarifications and preferences in the chat.

  • Each AI-generated transaction is pre-populated with all required fields for posting to QBO (date, amount, vendor/account, line items, etc.).

  • You can save the resulting selections as a new skill - or as an update to an existing skill - so the same multi-transaction logic can be reapplied next time.

  • Use Post all to send every transaction from the file to QBO in a single action.

Manual (ad hoc journal entries and bills/expenses)

  • From the Receipt review modal or Transaction review modal, click the More menu (β‹―) and select Multi-txn from file.

  • An Add transaction button will appear below the initial transaction.

  • Click Add transaction to create another transaction tied to the same file, with all of the configurable inputs for that transaction type in a new section below the previous one.

  • Manually added transactions are included in the bulk post to QBO alongside any AI-generated transactions.

  • Available across all supported AI transaction types (journal entries, bills, expenses).

Managing transactions in a multi-transaction receipt

  • Duplicate: click the three-dot menu on a transaction and choose Duplicate to create another transaction inside the receipt pre-filled with the source's values.

  • Remove: click the three-dot menu and choose Remove to delete that transaction (and all of its data) from the Transaction review area.

  • Change the receipt type: applies to all transactions in the receipt at once.

  • Add another file: adding a file to the receipt makes it available to all transactions inside the receipt.

  • Posting: you can't post the receipt while any transaction still has an error. Fix the error (or remove that transaction) and try again.

  • Partial failures: if some transactions post and others fail, the receipt will list both - posted and failed transactions are shown together so you can address the failures and try again.

Caveats and limitations

  • Multi-transaction receipts are disabled in the Quick Add menu.

  • You can't remove a multi-transaction receipt directly - remove the individual transactions inside it.

  • You can't duplicate a multi-transaction group at this time.

  • Client questions can't be accessed from a multi-transaction receipt.

  • Once a receipt is converted to a multi-transaction receipt, it can't be converted back and will need to be deleted.


Saving and reusing Skills

When the agent finishes its calculations, it may recognize that this transaction (or set of transactions) could become a reusable skill for the next time you upload a similar file. You can also save a skill manually based on the selections you made in the AI Composer.

Skills capture:

  • The transaction type and the prompt or instructions used

  • Your answers to the agent's clarifying questions

  • Account, class, location, vendor, and customer mappings

  • Multi-transaction logic when a single file is expected to produce multiple transactions

Saving selections as a skill also updates client-specific memory, so the agent applies your preferences with better context going forward.

Skill Manager

All of your skills are available from the Skill Manager, where you can:

  • Open and view existing skills

  • Edit a skill's instructions or mappings

  • Apply a skill to a new transaction

Smart skill updates

If your selections differ from an existing skill, the agent will ask if you'd like to update the existing skill based on your latest preferences and selections - instead of always creating a new one. This keeps your skill library tidy and ensures your saved logic stays current.


Reusing skills for recurring transactions

For recurring entries, upload the latest document and:

  • Open the file and select the transaction type

  • In the AI Composer, apply your previously saved skill (or reference a similar transaction)

  • Answer any clarifying questions the agent surfaces for this month's document

If you have a new document type, create a new skill and save it with a clear name.

Now you're ready to use AI Transactions to simplify your high-volume postings every month. Save time, reduce errors, make handoffs easier within your team, and get back to your high-value client work.

Did this answer your question?