> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/knowledge-base/integrations-help-guides/myob/myob-faqs.md).

# MYOB FAQs

Answers to common questions when integrating with MYOB.

<details>

<summary>How do I connect to MYOB?</summary>

Refer to our getting started guide — <https://help.tahua.io/getting-started-with-myob>

</details>

<details>

<summary>How do I disconnect from MYOB?</summary>

Refer to our getting started guide — <https://help.tahua.io/getting-started-with-myob>

</details>

<details>

<summary>How do I map a Tahua Applicant to an existing MYOB Supplier?</summary>

When a Bill is synced, Tahua matches the applicant to an existing MYOB Supplier where possible, and creates a new Supplier if no match exists. Suppliers are created inline during bill sync — there is no separate bulk contact upload for MYOB.

</details>

<details>

<summary>When does a Milestone get synced to MYOB as a Bill?</summary>

Milestones can be synced to MYOB at different points in the Milestone lifecycle, depending on your Organisation's needs.

You can choose which points you want to sync at from the MYOB settings under your Organisation settings by going to your Settings > Organisation menu and clicking on "Edit Details".

You can select multiple sync points if you wish. If you are not using Contracts within Tahua, then the only option that is applicable is "When the Milestone is approved".

You can read more about Milestone payments [here](https://help.tahua.io/knowledge-base/integrations-help-guides/myob/payment-integrations/milestone-payments-using-a-myob-integration.md).

</details>

<details>

<summary>Why hasn't a Milestone or Payment synced to MYOB?</summary>

If the Milestone shows a **Supplied by us** label, or its Payment shows an **Incoming** label, this is expected. These are [Organisation-supplied Milestones](https://help.tahua.io/knowledge-base/administrator-help-guides/milestones/organisation-supplied-milestones.md): obligations your organisation owes the Counterparty, where any Payment is money owed **to** your organisation rather than a Bill you pay.

Tahua never syncs them to MYOB, at any sync point. That means:

* no Bill or MYOB Supplier is created for them
* the **Retry sync to MYOB** and **Force payment sync** buttons don't appear on them
* payment status isn't pulled back from MYOB, so record the Payment in Tahua yourself once the money arrives
* their Payments are left out of the bank payment file when you export a Payment Batch

</details>

<details>

<summary>What account code are bills coded to in MYOB?</summary>

You are able to choose which account code your bills are coded to within your Tahua organisation settings.

Navigate to Settings > Organisation, click "Edit details", and set the **MYOB Account Code** field. This is the account code milestones will be created under.

If your organisation uses Funds, Milestone bills can be split into one line per Fund, each with its own account code. See **How are Milestone bills split when we use Funds?** below.

</details>

<details>

<summary>How are Milestone bills split when we use Funds?</summary>

If your organisation uses [Fund Management](https://help.tahua.io/knowledge-base/administrator-help-guides/fund-management.md) and a Milestone has Fund allocations, its MYOB bill has **one line per Fund** instead of a single line for the whole Milestone.

The allocations come from the Milestone itself if it has its own, otherwise from its Application and Contract combined. See [Allocating Funds](https://help.tahua.io/knowledge-base/administrator-help-guides/fund-management/allocating-funds.md).

* **Description** — each line is named after its Fund.
* **Amount** — the Milestone amount is split pro-rata to the allocations. Any rounding difference goes on the last line, so the lines always add up to the Milestone amount.
* **Account code** — each line is coded to the Fund's own MYOB account code if it has one. Otherwise it uses the account code the bill would otherwise have used, usually the **MYOB Account Code** in your organisation settings. Per-Fund MYOB account codes can't be set from the Fund page, so contact Tahua Support if your Funds need their own.

If a Milestone has no Fund allocations, the bill is created as a single line for the Milestone amount, as before.

If you add, edit or remove an allocation, any unpaid Milestone bills that draw on it are resynced automatically so the lines match. Paid bills are never changed.

</details>

<details>

<summary>How often is payment information synced back to Tahua?</summary>

Payment information is pulled from MYOB back into Tahua every 24 hours. You can also trigger it on demand at any time using the **Force payment sync** button on a milestone.

</details>

<details>

<summary>A Milestone bill failed to sync — what do I do?</summary>

Occasionally a Bill can't be created in MYOB (for example, an invalid account code, or a Supplier/Bill that has been changed or deleted in MYOB). When this happens, a report is sent to the **Milestone sync error email** address configured in your MYOB settings.

The email includes a link to inspect the Milestone in Tahua and manually retry the sync. When you retry manually, you can also choose a different date for the Bill if needed. A Milestone that has failed will show a **Retry sync** option in Tahua.

</details>
