Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The purpose of this help is to explain the process flow between BUZ and MYOB, what happens when you do specific functions in BUZ and how it affects MYOB. To do this, below are a series of scenarios that illustrate the data flow between BUZ and MYOB.

...

The Basic Scenario 1 illustrates an Order progressing in BUZ and how BUZ creates an order and then updates the status of that Order/Invoice within MYOB.

  • The order with a Deposit made in BUZ creates an Order in MYOB (along with an Allocated Receipt).

  • When the Order is Invoiced (yet not fully paid in full), the Order in MYOB will change its status to Open Invoice.

  • Once the Invoice is paid in full within BUZ, The status for the order will change to Closed Invoiced within MYOB.

Things to note here:

No Communication between BUZ and MYOB occurs until one of the following instances;

...

If an order is edited and the value is increased, MYOB will not reflect the change until an additional payment is made or the order is invoiced in BUZ.

Gliffy
imageAttachmentIdatt2207776785
macroId93bac511-9820-43f2-a0c8-d9d20505a788
baseUrlhttps://buzsoftware.atlassian.net/wiki
nameBUZTOMYOB New Scenario 2
diagramAttachmentIdatt2207744025
containerId2205777921
timestamp1638761661573

Basic Scenario 2

In Basic Scenario 2 a Deposit is paid, and an Invoice iscreated, and paid in full.

  1. The order and deposit raised in BUZ creates an Order in MYOB (along with an Allocated Receipt).

  2. When the Order is Invoiced and yet not fully paid in BUZ, means the Order in MYOB will change its status to Open Invoice.

  3. Then once the Invoice is paid in full in BUZ, the status will change again to Closed Invoiced within MYOB.

Gliffy
imageAttachmentIdatt2207350811
macroId7d1684fa-2a58-4b2f-bb12-31dcddafe0d8
baseUrlhttps://buzsoftware.atlassian.net/wiki
nameBUZTOMYOB New Scenario 3.1
diagramAttachmentIdatt2207154211
containerId2205777921
timestamp1638762798341

Basic Scenario 3

In Basic Scenario 3 no deposit is paid, an Invoice created, then paid in full (no additional payments are made before invoicing).

...

Gliffy
imageAttachmentIdatt2207252515
macroId4c0dbbac-9753-4ef2-b891-f68e79a8dfae
baseUrlhttps://buzsoftware.atlassian.net/wiki
nameBUZMYOBSenariC2
diagramAttachmentIdatt2208202755
containerId2205777921
timestamp16387657171711638756137739

Alternative Scenario 1: Order is Paid in Full then amount of order is reduced

...

  • An open order is paid in full in BUZ

  • The order is modified to reduce the price of the order.

  • When the order is raised and paid in full a corresponding Order is raised in MYOB along with the allocated payment for the entire order.

  • The amount of the order is adjusted to have a lower totalwithin BUZ. This prompts BUZ to guide the user to create a Credit Note in BUZ and create an Overpayment in MYOB.

  • The original order in MYOB is modified along with the payment allocated to the revised order total in BUZ.

  • A new Closed Invoice is created for the overpaid amount ( the difference between what was originally paid and the new total).

  • A new Credit Note is raised in MYOB for the difference between what was originally paid and the new order total in BUZ. The user can then elect to refund or otherwise allocate the credit within MYOB.

Gliffy
imageAttachmentIdatt2207219750
macroIdfc0c4137-5f6f-4acf-b87e-01e44cd2eda1
baseUrlhttps://buzsoftware.atlassian.net/wiki
nameBUZTOMYOBComplex2
diagramAttachmentIdatt2207744044
containerId2205777921
timestamp1638770225813

Alternative Scenario 2

In this scenario:

...

  • Invoice is raised and paid in full within BUZ.

  • Credit note is raised for the Invoice within MYOB.

  • User Allocates Credit Note within MYOB.

Complex Scenario 2

...

Image Removed

Payment and order total is updated in MYOB correctly

...

Image Removed

...