MYOB EXO
Content
Introduction
ProSpend is committed to enhancing expense management and accounts payable automation by enabling seamless integrations with popular finance systems. As part of this mission, ProSpend has developed an API integration with MYOB Exo. This integration allows ProSpend users to streamline their workflow by automating data transfer between ProSpend and MYOB Exo, making it easier than ever to manage financial processes across both platforms.
Overview
The ProSpend-MYOB Exo integration provides users with the ability to effortlessly push critical financial data, such as invoices and cashbook entries, directly to MYOB Exo from within the ProSpend platform. This API integration eliminates manual data entry, reduces the risk of human error, and ensures that data remains up-to-date across both systems.
In addition to pushing data to MYOB Exo, the integration also allows ProSpend to pull supplier information from Exo, enabling centralised and consistent supplier management within ProSpend. This bi-directional data flow streamlines accounts payable processes, improves data accuracy, and saves time by consolidating these tasks within a single, efficient workflow.
With ProSpend’s MYOB Exo integration, users can expect a more efficient and automated approach to managing expenses, invoices, and supplier records, ultimately leading to better financial oversight and operational efficiency.
Versions Supported
ProSpend Exo API version - v1
Xeno version - v1.1.1.7
Setup Required on Client's End
- Create a user in their Exo database with read and write permissions.
- Run some scripts in their Exo database. ProSpend will provide these scripts.
- Whitelist an IP address so ProSpend’s proxy server can access their Exo database. ProSpend will provide this IP address.
Details Required from Client
- SQL server hostname details (URL or public IP address)
- Port via which our server can access the above server
- Database name
- Username of the user created in the Exo database
- Password
Dataflow
Creditor Invoices
Supplier invoices, credit card claims and reimbursements can be exported as creditor invoices. Credit notes will also be processed creditor invoices but with negative quantity or price.
Mapping - Header
Exo API Field |
Exo Field |
ProSpend Field - Supplier Invoices |
ProSpend Field - Cash Claims |
ProSpend Field - Card Claims |
Notes |
|---|---|---|---|---|---|
AlphaCode |
Account |
Supplier code |
Claimant vendor code |
Credit card reference |
|
DueDate |
Payment due |
Invoice due date |
Claim to date |
Claim to date |
All the dates are in YYYY-MM-DD format |
InvNo |
Invoice no |
Invoice number |
Claim ID |
Claim ID |
|
TransDate |
Invoice date |
Invoice date |
Claim to date |
Claim to date |
All the dates are in YYYY-MM-DD format |
Ref1 |
Order no |
Custom free text field |
Custom free text field |
Custom free text field |
|
Ref2 |
Header Job code |
Activity code from first line |
Activity code from first line |
Activity code from first line |
|
BranchNo |
Branch |
Cost centre from first line |
|
||
Narrative |
Narrative |
Custom free text field |
Custom free text field |
Custom free text field |
|
SalesNo |
Salesperson |
Claimant employee code |
|
||
Notes
- Each claim in an export will have one header line.
Mapping - Lines
Exo API Field |
Exo Field |
ProSpend Field - Supplier Invoices |
ProSpend Field - Cash Claims |
ProSpend Field - Card Claims |
Notes |
|---|---|---|---|---|---|
StockCode |
Stock Code |
Project or custom field |
If there is a StockCode present in the request, the GLAccNo and GLSubAccNodetails are being ignored. Some restrictions will need to be setup in ProSpend, so users can choose only stock codes or only GL codes. |
||
GLAccNo |
GL Code - 2nd Segment |
Expense type |
If there is a StockCode present in the request, the GLAccNo and GLSubAccNodetails are being ignored. Some restrictions will need to be setup in ProSpend, so users can choose only stock codes or only GL codes. |
||
GLSubAccNo |
GL Code - 3rd Segment |
Custom field or activity code |
If there is a StockCode present in the request, the GLAccNo and GLSubAccNodetails are being ignored. Some restrictions will need to be setup in ProSpend, so users can choose only stock codes or only GL codes. |
||
Description |
Description |
Line description |
|
||
UnitPrice |
@Price |
If there is nothing in our price field, the "Gross Amount" value will be exported. If there is a value in the price field and if the tax flag says "Tax Inclusive", then the value in the price field will be exported. If the tax flag says "Tax Exclsuive", then the gross amount will be divided by the quantity entered and that value will be exported |
Split gross amount |
Split gross amount |
|
Quantity |
Qty |
If there is nothing in the line quantity field, "1" will be exported but if there is a value in the field, that will be exported |
Hardcode 1 |
Hardcode 1 |
|
TaxRateNo |
Options- GST rate |
Split tax code |
Split tax code |
Split tax code |
|
Location |
|
Custom field |
|
||
BranchNo |
GL Code - 1st Segment |
Cost centre |
|
||
BatchCode |
Batch Code |
Custom field |
Batch code will be ignored for GL lines. |
||
Narrative |
|
Custom field |
|
||
JobCode |
Job Code |
Activity code or custom field |
JobCode cannot be sent for GL lines. Again, some restrictions need to be setup in ProSpend. |
||
TaxInclusive |
|
True (Always inclusive) |
|
||
ExtraFieldName |
|
Can be configured in the background |
We allow up to 2 extra fields |
||
ExtraFieldValue |
|
Custom field |
We allow up to 2 extra fields |
||
Notes
- Each split/expense in an export will have one detail line.
MYOB Exo Cashbook Entries/Journals
Credit card claims can be exported as cashbook entries.
Mapping - Header
Exo API Field |
Exo Field |
ProSpend Field - Card Claims |
Notes |
|---|---|---|---|
Description |
Reference |
Claim description |
|
ChequeNo |
Cheque number |
Claim ID or export ID |
|
TransDate |
Date |
Date of export |
All the dates are in YYYY-MM-DD format. |
BankGLAccNo |
Bank account - 2nd Segment |
Credit card reference |
|
BankGLSubAccNo |
Bank account - 3rd Segment |
Will be hardcoded in the background |
|
Initials |
Entered by |
Can be hardcoded in the background |
|
PostType |
|
Can be configured in the background |
‘R’: Recurring, ‘P’: Post to GL, ‘S’: Suspended |
Notes
- Each claim in an export will have one header line.
Mapping - Lines
Exo API Field |
Exo Field |
ProSpend Field - Card Claims |
Notes |
|---|---|---|---|
LineLedgerType |
Lr |
X for expenses or splits with positive amounts and I for expenses or splits with negative amounts |
|
LineDate |
Date |
Expense date or date of export |
All the dates are in YYYY-MM-DD format. Line date when not provided, header Transdate will be applied to the line. |
LineDetails |
Details |
Line description |
|
LineRefNo |
Chq/Ref |
Expense ID |
|
LinePaymentTypeNo |
Type |
Can be configured in the background |
0 (Cash) 1 (Cheque) 2 (EFTPOS) 3 (VISA) 4 (Mastercard) 5 (AMEX) 6 (Diners) 7 (Direct Credit) 8 (Other) 9 (Direct Debit) 10 (Dishonour) 11 (EFTPOSCash) 12 (MPowered) |
LineExpense |
$ Expense |
If expense or split amount is positive, then expense or split amount including GST will be exported |
|
LineIncome |
$ Income |
If expense or split amount is negative, then expense or split amount including GST multiplied by -1 will be exported |
Refunds/credits will be incomes. |
LineAccNo |
A/c - 2nd Segment |
Expense type |
|
LineGLSubAccNo |
A/c - 3rd Segment |
Custom field or activity code |
|
LineBranchNo |
A/c - 1st Segment |
Cost centre |
|
LineTaxRateNo |
Options - GST rate |
Split tax code |
Even though we send tax rates, Exo seems to be setting correct tax codes. |
Notes
Each split/expense in an export will have one detail line.
Supplier Sync
Exo Field |
ProSpend Field |
|---|---|
Name |
Pay To |
AlphaCode |
Supplier Code for that integration |
TaxReg |
ABN |
Address1, Address2, Address3, Address4 and Address5 |
Concatenate into Address field |
Email Address |
Notes
- If "IsActive": true in API, then the supplier will be created or updated. If "IsActive": false, then the supplier will be disabled for that integration.
- The Payment Details field will be set to None as we don’t receive any payment details from Exo.
- Exo doesn’t seem to have separate address fields for city, state, post code and country, so we concatenate and put everything into one address field.
- Auto sync can be enabled in the background. This will be run every day at 10AM and 2PM Sydney time.
FAQs
Q. Can we push documents to Exo?
A. Documents cannot be pushed to Exo at the moment.