If you connect Float to NetSuite, you can export card transactions as native Credit Card Charge and Credit Card Refund records, instead of Journal Entries. This gives you cleaner reporting in NetSuite, as transactions show up in your credit card registers and reconciliation views, not just the general ledger. This makes it easier to reconcile against your statement.
This article explains how the setting works, how Float chooses which account a transaction posts to, and what stays the same.
Guide Summary
Two Ways to Post Card Transactions
How Float Chooses a Credit Card Account
Amortized Transactions Are the Exception
Two Ways to Post Card Transactions
Every NetSuite connection posts card transactions using one of two methods:
- Credit Card module: all eligible card transactions post as Credit Card Charges (purchases) or Credit Card Refunds (credits and refunds).
- Journal Entries: Float's original posting method. Each transaction posts as a journal entry against your clearing account.
You choose one method for your whole NetSuite connection. You can't post some cards or transactions through the Credit Card module and others as Journal Entries.
Since switching changes how your transactions show up in NetSuite going forward, Float asks you to confirm before the change takes effect.
New NetSuite connections default to the Credit Card module. If you're an existing customer, your connection stays on Journal Entries until you turn on the new setting; nothing changes unless you opt in.
Please note: We recommend picking one posting method, either Journal Entries or the Credit Card module, and sticking with it. Switching back and forth splits your card activity across two record types in NetSuite, which makes reporting and reconciliation harder to follow.
How Float Chooses a Credit Card Account
NetSuite tracks credit card balances using dedicated Credit Card GL accounts, separate from the accounts used for Journal Entries. Once you turn on the Credit Card module, Float replaces your clearing account fields with USD Credit Card Account and CAD Credit Card Account selectors, and only shows you GL accounts of the Credit Card type.
Float resolves which Credit Card Account a transaction posts to in this order, from most to least specific:
- Transaction-level override: set on an individual transaction from the export screen, before it's sent to NetSuite.
- Card-level override: set on a specific card, so every transaction on that card posts to a chosen account regardless of subsidiary.
- Subsidiary default: if neither override is set, Float posts based on the transaction's subsidiary and currency. For example, a transaction on your CA subsidiary posts to your CAD Credit Card Account.
This mirrors how subsidiary and currency defaults already work elsewhere in your NetSuite integration. You can route specific cards or transactions to a different Credit Card Account when needed.
Amortized Transactions Are the Exception
If a card transaction has an amortization template applied, it still exports as a Journal Entry, even if your connection uses the Credit Card module. NetSuite's amortization schedules run through Journal Entries, not the Credit Card module.
Everything else about amortization is unchanged. See Amortization Overview & FAQs for details.
Frequently Asked Questions
Can amortized transactions be exported through the Credit Card module?
No. Amortized transactions can only be exported to NetSuite as Journal Entries.
Should I switch between Journal Entries and the Credit Card module?
We recommend sticking to one posting method whenever possible (with amortized transactions being the exception).
You can switch posting methods, but it only affects transactions exported after the change, so switching often may result in your history being split across two record types.
Do refunds work the same way?
Yes. Refunds and credits post as Credit Card Refunds, matched to the same account logic as charges.
What happens if I edit and re-export a transaction?
Float updates the existing NetSuite record; it won't create a duplicate.
Do I need anything set up before I can export a transaction?
A vendor must be set on the transaction first. Float blocks the export with an error if a vendor is missing.
If I switch posting methods, does it affect transactions I already exported?
No. Switching between Journal Entries and the Credit Card module only affects transactions exported after the switch; anything already exported stays as-is.