Skip to main content

Purchase order settings reference

Look up PO integration, cost allocation requirements, approval routing and numbering options.

Written by Ben Walker

Use this reference to look up purchase order settings and their effects.

Finance features

Location: Settings → Features → Finance.

  • Allow PO integration for project costs: allows Drum costs to integrate with third-party finance purchase orders. Supported integrations include Xero and MYOB; QuickBooks support is planned.

  • Require purchase order allocation before approving a cost: when a cost is linked to a PO, every valued line must draw down on a PO line before approval. Costs with no PO link are unaffected and imports are not blocked.

Check your account’s current values on the Finance tab.

Purchase order approval

Location: Settings → Approval Settings → Purchase orders.

  • Document Type: Purchase order.

  • Approval Routing — Project Role: uses the specified role on the project.

  • Project Role: users with this role on the project are asked to approve. The example uses Project Director.

  • Can also be approved by (optional): selected account roles can approve in place of the primary approver.

  • Additional roles shown: Invoice Approval; Manager; Owner/Account Admin; Staff - no finance access; Staff - with finance access.

  • Save Setting: saves the approval configuration.

Direct-manager routing is also mentioned. Value-based approval layers are described as future functionality.

Purchase order numbering

Location: Settings → Finance Settings → Purchase Order Numbering.

  • Drum generates purchase order numbers: opt-in generation in Drum. When off, the finance system continues assigning numbers. Previously issued Drum numbers are retained either way.

  • Purchase Order Code Prefix / Suffix: text before or after the generated number.

  • First Part / Second Part / Third Part: up to three components. At least one is needed when generation is enabled; unused parts can be None.

  • Number Padding (if sequential number used): leading zeroes for the sequential component. The field indicates no padding by default and up to seven digits. Padding 3 gives 001 for sequence value 1.

  • Code Separator: separates components, for example with a dash or space. Blank means no separator.

  • Purchase Order Numbering Start (if all time sequence used): optional starting value for the all-time sequence. Field help says blank starts from 1.

  • Next Number: previews the next number or reports that the rule is not ready.

  • Longest this rule can produce: maximum possible length for the configured rule.

  • Save Purchase Order Numbering: saves the configuration.

Number components shown

  • None

  • Sequential Number (All Time)

  • Sequential Number (Current Year)

  • Current Year (Two Digit)

  • Current Year (Four Digit)

  • Current Month (Two Digit)

  • Sequential Number (Current Month)

  • Project Type Code

  • Project Number

  • Sequential Number (Project)

Number format restrictions

A prefix, suffix or separator cannot contain an asterisk (*) or apostrophe ('). MYOB rejects PO numbers longer than 13 characters. The numbering screen warns when the longest possible number exceeds this limit and explains that MYOB-assigned numbering is retained until the rule fits if the account connects to MYOB.

A legacy numbering-start field is marked as no longer applicable for the demo account’s join year. Use the active all-time start field where applicable.

Did this answer your question?