Please build a QuickBooks import file from my FlipperForce books for [DATE RANGE].
1. Ask me which QuickBooks import path I am using and which projects to include. If I have no preference, produce a bank register style CSV with one row per expense line item.
2. When I paste in my QuickBooks chart of accounts, map every FlipperForce expense category and expense account to one of my QuickBooks accounts. Show me the mapping table and wait for my confirmation before you build the file.
3. Pull the expense line items for each project in the date range with vendor, date, description, invoice number, amount, tax and total. Pull the income records for the same range and the same projects.
4. Put the project name in the class column on every row so my job costing survives the import.
5. List anything you could not map cleanly in a section called Fix before importing. Line items with no vendor, no category, or an amount sitting in a generic bucket, plus any two rows that look like the same transaction entered twice.
6. Give me the mapping table, the exceptions list, and the file itself, with row counts and totals I can tie back to FlipperForce before I import anything.
Change nothing in FlipperForce.
This is an export, not a sync. There is no live connection between FlipperForce and QuickBooks, and nothing here writes to either side. A two way QuickBooks integration is on the public roadmap.
Expenses and income are read one project at a time, so a full year across a large portfolio is a lot of requests. Scope it to a quarter and a project list if you run many projects.
You enter an expense in FlipperForce because that is where your job costing lives. Then you or your bookkeeper enter it again in QuickBooks because that is where your tax return comes from.
Double entry is the most upvoted complaint we have. Until a real sync ships, the fastest way to stop retyping is to stop typing and start importing.
Your assistant reads every expense line item and income record in the range, maps your FlipperForce categories and accounts to your QuickBooks chart of accounts, and writes a file you can import. The project name rides along in the class column, so the job costing you already do in FlipperForce shows up on the other side.
The exceptions list is the part that earns its keep. Unattributed spend and duplicate looking rows get caught before they are in your books instead of at year end.
What it will not do: this automation is read only and one directional. It does not connect to QuickBooks, log in to QuickBooks, push anything into QuickBooks, or pull QuickBooks transactions back into FlipperForce. It produces a file. You review it and you import it.
This prompt requires a connection to the FlipperForce Public API. Once your AI agent is connected to your account, you can run any prompt in the library.
Learn how to connect your AI agent to the FlipperForce Public API
Before you run this, check:
Import into a QuickBooks test company the first time. Get the mapping right once and every run after that is a two minute job.