You can now split Float transactions into multiple line items to properly allocate them to different expense categories
Guide Overview
When Should You Split a Transaction?
How to Split a Transaction Before Exporting?
How do Split Transactions Look Once Exported?
- Split transactions in QBO
- Split transactions in Xero
- Split transactions in NetSuite
- Split transactions for CSV Export
When Should You Split a Transaction?
When accountants have multiple fees in one expense on Float, that should belong to different expense categories (GL codes). This feature can be used for situations such as…
- Subscription fee vs licensing fee
- Splitting out alcohol vs client gifts from an LCBO receipt
How to Split a Transaction Before Exporting?
For steps on splitting transactions, see:
How to Split a Transaction from the Transactions Page?
Note that transaction splits must be enabled for the business to allow Spenders and Managers to split transactions. See: How to Enable Transaction Splits?
How do Split Transactions Look Once Exported?
Split Transactions in QBO
In the image below, we have split the Ramen and Egg into separate classes, and they appear as separate line items on the Float CAD account.
Split Transactions in Xero
In the image below, we have split the Ramen and Egg into separate departments, and they appear as separate line items on the Float CAD account.
Split Transactions in NetSuite
In this example, instead of splitting GL codes, we decided to split different "descriptions" per cookie order. These all have the same Account but different descriptions on Float, which translate into different "memos" in NetSuite.
Split Transactions for CSV Export
We recommend using a Custom CSV Template (instead of the Standard CSV) when using Split Transactions. When exporting a split transaction using a Custom CSV Template, you will see one row for each line item of the transaction in the CSV.
If you’re using our Standard CSV Export, you will see new columns appended to the end of your CSV for each new line item.