Figena
Move through a consistent workspace without flattening the facts that make bank, card, and cash accounts different.
Every account uses the same workspace, permissions, activity, and review language. Type-specific facts stay native.
The account workspace changes its facts and review flow according to the account you are managing.
A bank balance is only useful when its source, update time, imported activity, and reconciliation state are visible.
Use the available ingestion path and keep its source explicit. Provider availability varies and is never presented as universal real-time connectivity.
Resolve unmatched or incomplete activity, then reconcile against the statement period before treating the balance as reviewed.
Current liability, statement balance, minimum due, due date, and utilization stay attached to the card account.
Record repayment intent and autopay configuration without implying that Figena executed the bank debit.
Link card repayments to the funding account so an internal movement is not mistaken for a second expense.
Keep expected and counted amounts separate, with location, custodian, count mode, variance, and approval evidence.
Counters can record the physical amount before seeing the expected value, then review any variance.
Variance adjustments preserve the reason and approval state. This is a cash-control workflow, not a claim of point-of-sale connectivity.
Use the same controlled path across every account while applying the right review for its type.
What changes when bank accounts, credit cards, and cash share one account workspace.
Bring bank, card, and cash records into a workspace designed for traceability, review, and accurate reporting.