Clarification Needed on New E‑Invoicing Fields for NZBN Usage

Himanshu

February 12, 2026 07:02

• Account name - Tataki Auckland Unlimited
• Region - APAC
• Client version (Enterprise) - 25.4
• Description of the issue: The customer has identified three newly added E‑Invoicing fields in the AR Demographics window. They want to understand the intended purpose of these fields and whether they should be used to store the NZBN ahead of future E‑Invoicing implementation.
  • What does the client want to do? Why do they want to do this?
    • They want to prepare their data model early for an upcoming E‑Invoicing rollout. To do that, they need confirmation on the correct use of these fields, including whether NZBN belongs in one of them. This helps them avoid rework and ensures correct configuration.
  • Please give a descriptive user story. Often clients want to solve a problem by doing X. If we know the problem, sometimes it can be solved via Y.
    • As a customer preparing for E‑Invoicing in New Zealand, I want clarity on which Enterprise fields should store the NZBN, so I can correctly update and label AR records and avoid future data corrections once the feature is fully implemented.
• What you've already tried or suggested. Why does this not work?
  • Advised the customer not to make any changes until Product confirms the correct field usage.
  • Reviewed the E‑Invoicing in Enterprise documentation.
  • Informed them that historically the Tax ID field has been used for AU/NZ identifiers.
    Documentation does not confirm whether the new E‑Invoicing fields replace or supplement the Tax ID field, so guidance remains unclear.
• Business impact if not resolved
  • Risk of misconfigured data, potentially requiring large-scale rework.
  • Delays in preparation for E‑Invoicing.
  • Uncertainty in resource planning for updating customer account data.
• Attach relevant files (such as screenshots)

  • 

• Links to articles where you've looked for solutions and also other steps you've taken to research the issue.
  • https://connectsupportcenter.ungerboeck.com/hc/en-us/articles/38023876014487-E-Invoicing-in-Enterprise 

@... Pieter Du Plooy - Any insights! Thanks

• 

  Seth Halvaksz

  February 12, 2026 12:11

  Following
• 

  Linda Moyer

  February 12, 2026 14:57 Edited

  We debated about including the E-Invoice ID field in the docs and didn't. It is not being used at this time in the integration so I would recommend removing it from their layout to avoid confusion. I've added guidance to the article.

  It sounds like NZBN is a tax ID? If so, it should go in the existing Tax ID field. @... Can you confirm? If so, I'd love examples from different target countries so I can include those in the doc.
• 

  Himanshu

  February 13, 2026 02:57

  Thanks Linda - that's helpful. I will advise the customer to remove those fields from the layout for now.

  In Australia, we have ABN – Australian Business Number and in New Zealand, we have NZBN – New Zealand Business Number – these are your public‑facing business identifiers similar to the way US businesses use their DUNS number which i assume.

  In Australia, we have TFN – Tax File Number and in NZ we have IRD Number – Inland Revenue Department Number – these are actually the taxpayer identification numbers closer to a US EIN. I think right now there may be some regional differences on how everybody uses Tax ID fields to store this. If it helps, I received confirmation from the customer that they use NZBN currently under a UDF. This is due to historic configuration and they have some issues managing this for suppliers as well. They are currently storing the IRD number in the Tax ID field, and the idea is to move away from using a UDF where possible and pick the best field for the NZBN.

  @... – could you please confirm whether storing IRD in the Tax ID field is the correct long‑term guidance, and which standard field we should be using for NZBN going forward? (may help us rolling out data consistency)
• 

  Himanshu

  February 19, 2026 00:34

  Adding specs as provided by customer to facilitate future development of E-invoicing. Also happy to connect with customer as they are keen on participating with development of this.

   

  
• 

  Chai Hoang

  February 23, 2026 15:55

  Himanshu, sorry for the slow response - I'm just returning from PTO. We don't yet have the details for NZ so please be mindful that final design might change. 

  For now though, IRD in the Tax ID field and NZBN in the e-invoice ID make sense - the current plan is to use the e-invoice ID for any regional specific needs and having the E-invoice Scheme identify that regional specific scheme. For invoice method, they can switch it to “e-invoice”, but it won't do anything until there's an integration available. If they don't want to do that up front, we have a way for them to edit multiple after the fact.
• 

  Himanshu

  February 26, 2026 21:55

  Thanks @... for helping out.
• 

  Himanshu

  March 08, 2026 23:52

  @... - Another question that came through from the customer per below for Supplier Accounts, how would we manage this? I reviewed the articles, configuration and confluence pages but was unable to find.

  The e-invoicing fields are not available on the supplier accounts via the A/P Demographics screen. Where will the NZBN for receiving e-invoice from suppliers be facilitated?

Please sign in to leave a comment.