Where do I find the vendor documentation for a named invoice-matching application, and how does it describe the matching function?

Where is the authoritative documentation?

How you reach the documentation depends on how the vendor makes it available:

Product pages, pricing pages and app-store listings sell the function; they are not its documentation. NetSuite's Third-party SuiteApps page (undated) describes SuiteApp.com as a place to read customer reviews, try out solutions and find out where to buy.

Which edition, module and release does it cover, and does your business run it?

Documentation can be authoritative and still describe something your deployment lacks. Microsoft's Feature management overview says environments must be updated to receive changes, so a current page can describe a newer release than the one you run. Confirm four things before reading closely:

• Edition. Neither Microsoft's matching pages nor NetSuite's 3 Way Match topic names an edition, so ask your administrator or the vendor which edition you run and whether the topic covers it.
• Release. Nor do they name a release: Microsoft's show only a last-updated date and NetSuite's none, so record the page's date, or the date you read it. Get your release from the administrator; NetSuite's help also lists a topic titled Finding Your NetSuite Release Version. If your release differs from the newest one on the vendor's list, such as Microsoft's What's new or changed in Dynamics 365 Finance page, which links release notes for each release, close the gap through release notes or a written support question.

• Module or feature enabled. Microsoft's matching setup page, Set up Accounts payable invoice matching validation, says to make sure the Invoice matching configuration key is selected before you begin. Microsoft's License codes and configuration keys report page says purchasing finance and operations gives you all functionality, and that the administrator should disable unneeded features through license codes and configuration keys, which removes them from the user interface, so ask the administrator before treating a missing module as unpurchased.

  Microsoft's Feature management overview says its workspace lists the features delivered in each release and lets you enable or disable them, and that an enabled feature is available only to users whose security role gives them access, and only in legal entities they can access.

• Add-on installed. NetSuite's 3 Way Match topic (undated) says the workflow is included in the NetSuite Approvals Workflow SuiteApp, which must be installed in your account.

If a screen the documentation describes is missing, check release, feature, license code, configuration key and add-on before treating it as a licence or access question.

Who owns the documentation when an add-on or connected service does the matching?

A native module is documented with the application; an add-on or connected service may be documented by another publisher, with its own releases and its own words for the same function.

NetSuite's SuiteApps page (undated) says SuiteApps are developed by Oracle NetSuite or by members of the SuiteCloud Developer Network, or built as custom SuiteApps by or for the customer, and that the Owner column on the Installed Bundles page shows each SuiteApp's developer. NetSuite's Third-party SuiteApps page (undated) says third-party SuiteApps are developed and supported by those partners and other third parties.

Identify the owner first. On pages a SuiteApp provides, NetSuite's Accessing the Help Center page says the Help link may open only the help center home page, so use the help center's SuiteApps link, which NetSuite's Using the Help Center Window page (undated) says shows where to find information about third-party SuiteApps, and ask the publisher for its documentation and release notes. Treat a SuiteApp.com listing as a route to the publisher. Read the add-on publisher's documentation for the matching logic and the core application's documentation for the records it supplies, list where the two name the same thing differently, and reconcile those terms before relying on either.

Which terms should you search for?

Search for these five things. The Microsoft terms come from its matching overview and matching setup page, and the NetSuite terms from its undated 3 Way Match topic:

The same word can mean different checks. Microsoft's matching setup page says two-way matching compares the invoice unit price with the purchase order unit price, and three-way matching also compares the invoice quantity with the matched product receipt quantity. NetSuite's 3 Way Match topic says the workflow validates a vendor bill against its purchase order and item receipt, and lists a difference in terms and location among its purchase order checks. Map each vendor term to the comparison it performs, not to the word your team uses.

How do you read what the matching function does and will not do?

Read the matching topic for four answers, in the vendor's own words:

• Inputs. The table's Documents compared row lists the records each topic names.
• Comparison. Microsoft's matching overview says matching discrepancies are compared with the tolerances that are specified.
• Result. Microsoft's matching overview says match variance icons are displayed when a discrepancy exceeds the tolerance percentage or amount. Microsoft's matching setup page adds a choice between requiring approval before an invoice with discrepancies can be posted and Allow with warning, under which the invoice can still be posted.
• Stated limits. Microsoft's matching overview says charges matching is performed only on charges codes set to compare purchase order and invoice values, that on a partly invoiced purchase order line price-total validation occurs on the last invoice for that line, and that other forms of invoice validation use vendor invoice policies. NetSuite's 3 Way Match topic (undated) says item receipts that have been partially received are not supported.

A match result compares documents; it does not confirm where the money goes. A bill or message that changes a vendor's payment details needs verifying before anything is paid, as a separate question. Running a match, and handling an invoice that matches no purchase order, are also separate questions.

What will the configuration documentation ask your business to decide?

Microsoft's matching setup page asks for these decisions:

• Enable. Decide whether invoice matching validation is enabled at all.
• Default policy. Choose a line matching policy for the legal entity and whether it can be overridden for an item, vendor, item and vendor combination, or purchase order line; the legal-entity default applies to every item and vendor without a different policy.
• Tolerances. Set price tolerance percentages for the legal entity, items and vendors. The legal-entity default price tolerance is zero percent, and negative price discrepancies are allowed by default; tracking them means choosing If greater than or less than tolerance in the Display unit price match icon field.
• Posting. Decide whether approval is required before an invoice with discrepancies can be posted. If you use workflows with matching validation, Microsoft says to set Post invoice with discrepancies to Allow with warning.
• Timing. Decide whether matching runs automatically during invoice data entry. Microsoft recommends automatic matching unless data entry performance is a concern. With automatic updates off, validation is bypassed during entry and the clerk must update the match status manually to see results.
• Other checks. Decide whether to match invoice totals, price totals where a vendor sends several invoices for one purchase order line, and charges. A legal entity that tracks expenses such as freight by using charges also needs the Charges configuration key selected.

NetSuite's 3 Way Match topic (undated) raises different decisions: installing the SuiteApp, whether to modify the workflow, which it says serves as a template, choosing which exception criteria to disable, and, when using the tolerance fields and criteria, disabling other quantity and amount criteria that may affect the validation.

How do you tell documented behaviour from marketing and community claims?

Treat as documentation what the vendor designates as its documentation. NetSuite's Accessing the Help Center page says the help center contains all technical documentation you need to learn how NetSuite features work, and Microsoft's Feature management overview says a feature's Learn more link opens the documentation for the feature.

Forward-looking material states intent. Microsoft's 2025 release wave 2 plan for Dynamics 365 says its release plans describe functionality that may not have been released yet, and that delivery timelines and projected functionality may change or may not ship.

Community posts report experience, not documentation: NetSuite's Using the Help Center Window page describes the NetSuite Community as a place to share information, experience and advice with application users and NetSuite employees.

What does the documentation leave unsaid, and how do you close the gaps?

Put your own cases to the four answers: partial receipts, several invoices against one line, credits, charges, currencies and purchase orders changed after the invoice arrives. Where the page says nothing, record a gap, not a "no".

Close each gap in one of three ways:

• Release notes. Read the release notes between the release you run and the newest one, looking for changed matching behaviour and new settings. NetSuite's Using the Help Center Window page links to release notes for the newest release.
• Support. Ask the documentation owner in writing and name your release. NetSuite's SuiteAnswers Overview (undated) says that from SuiteAnswers you can submit a question or issue by email or contact NetSuite Customer Service by phone.
• A test outside production. Observe the configured function on your cases before it acts on real invoices. Microsoft's Environment planning page says the standard cloud offer's acceptance-testing instance is a non-production instance customers can use for UAT, integration testing and training. Without such an environment, ask the vendor or partner how to observe the behaviour first. Microsoft's Feature management overview says environment update timing is variable, so before relying on any test, confirm the test environment matches production's release, features, configuration keys, add-ons and matching parameters, record both, and retest after either is updated.

What if an implementation partner configured the deployment?

Then what the documentation says the function can do and what your configuration makes it do are separate questions. Microsoft's matching setup page shows why: the legal-entity policy can be overridden for a specific vendor, item, combination or purchase order line, so one vendor's invoices can be matched differently from the default. Purchase order lines also carry their own Matching policy field, so check it on sample open purchase orders. Establish your configuration by reading the configured values on the setup screens, asking the partner for its written configuration with the reason for each value, and confirming both in the test outside production. In NetSuite, where a partner has customised the 3 Way Match workflow, read it as configured in your account.

How do you record the documented behaviour against its release?

Keep your own matching reference, recording:

• The application, edition, release or build, and the module, feature or add-on with its publisher
• Each page's title, address and date, and the date you read it
• The four answers in the vendor's words, and each configured value with who chose it
• Each gap and how it was closed, with the release note, support case or test date

Documentation also changes between releases: NetSuite's Using the Help Center Window page offers Help Center Weekly Updates, a list of recent changes made in the help center. Compare the reference with the documentation and release notes at each release, so a product change shows as a divergence, not a misunderstanding.

What does a location-and-applicability check look like?

Run it in this order:

1. Name the application, edition and release, confirmed with its administrator.
2. Establish who owns the matching function: the application vendor, the vendor's own add-on, a third party or a custom build, whose builder you ask for its specification.
3. Reach that owner's documentation through its documentation site, the in-product Help link or its customer portal, and note each page's title, address and date.
4. Confirm the function is licensed, enabled, installed and visible to your role.
5. Compare the setup screens with the documentation, then observe your own cases outside production, in an environment confirmed to match production.
6. Record the result against the release.