Expense management platform
Implement an expense management platform with the Blnk Ledger.
Efficiently managing expenses is crucial for both personal and business finances. This guide will help you implement a comprehensive expense management system using the Blnk Ledger.
We’ll learn about:
- Defining and creating your ledger structure
- Balance (expense account) creation
- Recording expenses
- Approving expenses
- Best Practices (with Inflight)
1. Ledger Structure
The entry point of the Blnk ledger system is ledger folders. These folders serve as a way to group and manage assets, accounts, and balances that fit your product or organization’s structure.
In this guide, we’ll use the following structure:
- Marketing Ledger: Contains all expense accounts for the marketing department.
- HR Ledger: Contains all expense accounts for the HR department.
The ledger structure is flexible and can be customized based on your specific needs. For instance, you could group by users instead of currencies, or use a combination of both.
See also:
Creating a marketing ledger
View your ledgers in your terminal:
blnk ledgers list
Always store the ledger_id in your database. You’ll need it for future operations related to this ledger.
Creating an HR ledger
2. Balance (expense account) creation
Blnk uses the concept of ledger balances to manage accounts/balances in a ledger. In this example, we’ll create expense accounts for various categories within each department.
See also:
Creating a marketing expense account for advertising
View your balances in your terminal:
blnk balances list
The balance_id is crucial. Always store this in your database and associate it with the customer. You’ll use this ID for all future transactions involving this loyalty point account.
Creating an HR expense account for recruitment
3. Recording expenses
Whenever a department incurs an expense, you can record it using the Inflight feature to manage the expense transactions.
See also:
Recording an advertising expense for marketing
View your transactions in your terminal:
blnk transactions list
Using inflight allows you to be able to set and apply approval rules on the transaction. If it is approved, the inflight transaction is committed. If it is declined, the transaction is voided.
Recording a recruitment expense for HR
4. Approving expenses
After recording an expense, it needs to be approved before being finalized.
Approving an advertising expense for marketing
Approving a recruitment expense for HR
See also
Managing side effects with Inflight
A deep-dive guide into how to implement Inflight in your application.
Best practices (with Inflight)
- Available Balance Calculation: In your application, calculate the available balance to prevent users from accessing funds that are held in Inflight transactions. This can be done as follows:
const availableBalance = balance - inflight_debit_balance; - Error Handling: Implement robust error handling in your Inflight process. If a commit or void operation fails, you may need to retry or escalate to manual intervention.
- Approval Process: Implement a clear approval process for expenses, including notifications and roles for approvers. This helps ensure that all expenses are reviewed and authorized properly.
- Reconciliation: Regularly reconcile your internal records with Blnk’s transaction logs to ensure accuracy. Pay special attention to Inflight transactions. Blnk v1 will support reconciliation features built into the ledger, which can aid in this process.
- Webhook Authentication: In a production environment, implement a mechanism to verify that webhooks are genuinely from your payment provider. This helps in maintaining the integrity and security of your transaction processing.
- Data Security: Always ensure that sensitive card details are securely managed and stored. Mask or encrypt card numbers, CVVs, and other sensitive information when storing or displaying them.
- Transaction State Management: Use metadata to manage the state of virtual cards and transactions effectively. For example, track the transaction verification status (e.g.,
VERIFIED,DECLINED) in the metadata. - Compliance: Ensure that your virtual card issuance and transaction processing comply with relevant regulations and standards, such as PCI-DSS for handling card data securely.
- Testing: Thoroughly test your virtual card issuance and transaction processing flows, including Inflight handling, to identify and resolve any issues before going live.
Need help?
We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool.
To ask questions or discuss issues, please join our Discord community.
Was this page helpful?