Automate classification and synchronization of expenses between your application and your customer’s preferred accounting service
Authorize end user
Your customer must first authorize your application to access their accounting service (e.g., Xero, Lexware Office, Sevdesk) via the respective authentication mechanism (e.g., OAuth2, API key) through maesn Connect.
Compile chart of accounts
Implement the following logic in your application to retrieve customers’ account data:
classification
(e.g., ASSET, EQUITY, EXPENSE, LIABILITY, REVENUE) to group accounts.parentAccount
to visualize hierarchical relationships in the customer’s General Ledger (GL).Synchronize contacts (optional)
Follow the steps outlined in the synchronize contacts use case to synchronize suppliers in your system with your customer’s accounting system.
Fetch dimensions
If your customer has classes, locations, or departments configured, you can retrieve them from the accounting service with GET /dimensions.
Setup categorization rules
Presenting the data retrieved in the previous steps in your frontend, enable your customer to configure rules for categorizing the expenses that will be synchronized to the accounting system. The business logic will depend on your application, but bear in mind that:
Synchronize expenses
Whenever your customer incurs spend-related transactions in your application, e.g., credit card transactions or travel expenses, you can synchronize the transactions to your customer’s Accounting system with the correct classification via the POST /expenses endpoint. It is up to your application whether these transactions should be synchronized automatically or require an end user to manually export the expenses from within your application.
Keep your data fresh
After fetching data initially, you should make sure to keep your customer’s data up to date by regularly retrieving data from the maesn API and looking for changes. The lastModified
query parameter can be utilized on all our GET endpoints to save you the hassle of creating deltas to detect change. See our guide to keeping data fresh for more information!
Automate classification and synchronization of expenses between your application and your customer’s preferred accounting service
Authorize end user
Your customer must first authorize your application to access their accounting service (e.g., Xero, Lexware Office, Sevdesk) via the respective authentication mechanism (e.g., OAuth2, API key) through maesn Connect.
Compile chart of accounts
Implement the following logic in your application to retrieve customers’ account data:
classification
(e.g., ASSET, EQUITY, EXPENSE, LIABILITY, REVENUE) to group accounts.parentAccount
to visualize hierarchical relationships in the customer’s General Ledger (GL).Synchronize contacts (optional)
Follow the steps outlined in the synchronize contacts use case to synchronize suppliers in your system with your customer’s accounting system.
Fetch dimensions
If your customer has classes, locations, or departments configured, you can retrieve them from the accounting service with GET /dimensions.
Setup categorization rules
Presenting the data retrieved in the previous steps in your frontend, enable your customer to configure rules for categorizing the expenses that will be synchronized to the accounting system. The business logic will depend on your application, but bear in mind that:
Synchronize expenses
Whenever your customer incurs spend-related transactions in your application, e.g., credit card transactions or travel expenses, you can synchronize the transactions to your customer’s Accounting system with the correct classification via the POST /expenses endpoint. It is up to your application whether these transactions should be synchronized automatically or require an end user to manually export the expenses from within your application.
Keep your data fresh
After fetching data initially, you should make sure to keep your customer’s data up to date by regularly retrieving data from the maesn API and looking for changes. The lastModified
query parameter can be utilized on all our GET endpoints to save you the hassle of creating deltas to detect change. See our guide to keeping data fresh for more information!