{
  "question_id": "CG-P1B-FULL-039",
  "slug": "how-a-vendor-invoice-management-system-is-set-up-and-run",
  "display_title": "How is a vendor-invoice-management system architected, configured and operated to process AP vendor invoices — its components, invoice capture and data extraction, routing and approval flow, the processing workspace and entry points, and its reporting over invoice processing?",
  "format": "article-v2",
  "applies_to": {
    "countries": [
      "US"
    ],
    "frameworks": [],
    "tax_year": null,
    "platforms": []
  },
  "general_concept": true,
  "summary": "Treat the system as eight components with separate jobs: ingestion channels, extraction, a validation and business-rule layer, approval workflow, the operator workspace, a posting integration, a document repository and reporting. Configure them in dependency order: ledger master data first, then validation rules and tolerances, then access and routing, then capture settings and channels. Keep every exception inside the workspace, monitor approved-but-unposted invoices, and budget ongoing effort for extraction upkeep, vendor onboarding and rule maintenance after go-live.",
  "body": "## What are the components, and what does each one own?\n\nPlace each configuration decision in the component that owns it before changing anything.\n\n| Component | What it owns |\n|---|---|\n| Ingestion | Arrival channels, file acceptance rules, the first duplicate screen |\n| Extraction | Reading fields from images, confidence scores, the model behind them |\n| Validation and business rules | Vendor and entity lookup, mandatory fields, totals, duplicates, matching tolerances |\n| Workflow routing | Approvers, conditions, delegation, escalation, timeouts |\n| Processing workspace | Queues, statuses, work assignment, the actions allowed at each status |\n| Posting integration | Turning an approved invoice into a ledger entry and catching failed posts |\n| Document repository | Keeping the source image attached through to the posted record |\n| Reporting | Volume, cycle time, exceptions and pending time in the system's own processing |\n\nScreen names, settings and behaviour below are Microsoft's, as documented on Microsoft Learn pages updated between August 2025 and August 2026. Microsoft's installation page says attachment document types need Finance 10.0.39 or later, so confirm attachments reach Finance before enabling Auto invoice cleanup. Microsoft's automation overview says the tax override must first be enabled in Feature management in 10.0.45 and 10.0.46. Invoice capture, which Microsoft's Invoice capture overview says automatically creates vendor invoices from digital invoice images, is a separate application that Microsoft's installation page says supports only integrated Power Platform environments, and Microsoft's Invoice capture workspace page says captured invoices are converted to vendor invoices in Dynamics 365 Finance. In another product, confirm the equivalent setting in that vendor's documentation before relying on any behaviour below.\n\n## How do embedded, integrated and capture-only topologies differ?\n\nThe topology decides which components exist and where a failure can hide.\n\n| Topology | What changes |\n|---|---|\n| Embedded module | Validation, workflow and posting run inside the ledger on its own master data. Microsoft's Vendor invoice center page describes one Finance workspace showing vendor invoices at every stage. No transfer can fail, but an approved invoice can still sit unposted. |\n| Integrated application | Capture, extraction and first-pass validation run outside the ledger and a transfer creates the ledger document, so master data must be synchronised and the transfer monitored. Microsoft's scanned-documents page describes a standard interface that any compliant external system can feed with invoices and attachments. |\n| Capture-only front end | A person keys or imports the extracted data and nothing posts automatically, so validation, approval and duplicate checks must all exist in the ledger or the procedure around it. |\n\n## Which entry points feed the system, and what does each fix downstream?\n\nEach entry point decides what arrives with the invoice and what later components must work out:\n\n- **Email and shared folders.** Microsoft's channels page says administrators define channels on triggers in Power Automate connectors, with templates including a Microsoft Outlook 365 shared mailbox. A legal entity assigned to a channel is assigned automatically to invoices received through it, so one channel per entity removes a derivation step.\n- **Scans and uploads.** Microsoft's channels page says files sent through configured channels land on the Received files page, but Microsoft's configuration page says a channel's flow doesn't receive files that fail the flow's criteria. That page's file filter sets minimum and maximum accepted file sizes, and the received-files page says files breaking the filter wait in Received file (pending) for Void or Retry.\n- **System feeds.** Microsoft's channels page describes a Document receive API that other systems use to send invoice documents, and says a call without a valid channel ID is ignored, never reaching Received files. The scanned-documents page's interface accepts structured header and line data with attachments.\n- **Supplier portal.** On Microsoft's vendor collaboration page, the vendor keys the invoice and a supplied PO number links it to the purchase order. Microsoft's automation overview says these invoices must be submitted to workflow manually.\n- **Manual entry.** Keyed invoices skip capture, and the automation overview says they join automated processing only when a user includes them.\n\nStructured invoices bypass extraction and confidence handling. A third-party feed through Finance's data-entity interface skips Invoice capture, an alternative source in Microsoft's automation overview, so Invoice capture's duplicate screen, derivation and validation checks never run. The feed's first checks are the import (Import failed), matching validation, posting validation and the imported-amount comparison: the automation overview says an imported invoice can post only if its imported values match the calculated values, unless the tax-override option is chosen. Decide whether the sending system or Finance checks vendors and repeated invoice numbers.\n\n## How is capture and extraction configured and kept accurate?\n\nExtraction accuracy is maintained, not bought, so staff the correction loop from the first day.\n\nMicrosoft's Invoice capture configuration page says the prebuilt model handles the most common invoices, while complex layouts need a custom model trained on uploaded, tagged sample invoices. The same page says custom models return no confidence scores, key-value pairs or currency codes, so for vendors read by one, rely on mandatory-field and totals checks rather than confidence thresholds.\n\nMicrosoft's configuration-groups page says confidence scores run from 0 through 100, administrators set thresholds that raise messages of different severity, and each group defines whether warnings or only errors require manual review. Where a group requires review only on errors, an invoice with no errors transfers to Finance without review; where it requires review on warnings, any warning holds the invoice in Captured. The page adds that prebuilt-model confidence scores don't improve with customer data and low scores mostly sit on accurate text, so expect threshold warnings to persist and staff review for them. That page says enabling the Use confidence score processing rule applies threshold validation, while the configuration page says selecting it skips that validation, so test that a low-confidence invoice raises its warning.\n\nMicrosoft's workspace page describes a side-by-side viewer that connects each field to its place on the original document; on that page, a clerk fixes a misread field by remapping it, and with continuous learning on, the system applies the change to later invoices from the same vendor. The same page says remapping works only with the prebuilt model and for invoices received after upgrading to Invoice capture 1.1.0.32; custom models use custom field mapping. The configuration page adds that the pattern is recorded only after the invoice transfers successfully. The workspace page advises against relying on mapping rules instead, because their maintenance load is high.\n\n## Where do validation and business rules live?\n\nThe system's checking lives in this layer, not in the workflow. Microsoft's Invoice capture pages describe these checks:\n\n- **Vendor lookup.** The workspace page says the vendor account is derived from mapping rules, the legal entity and the vendor's name, address or tax number, and processing stops if a derivation fails.\n- **Mandatory fields.** The configuration-groups page lets each group mark fields mandatory, applying groups by vendor account first, then legal entity, then system level.\n- **Existence.** The workspace page's existing check confirms that the legal entity, vendor, item, procurement category or purchase order exists.\n- **Totals.** The configuration page's Validate total amount rule compares the calculated total with the captured total. It runs only if its parameter is selected and skips invoices with no lines or a zero line total, so header-only invoices need another check.\n- **Duplicates.** The received-files page says the duplicate check compares file checksums, and that an invoice-number check does not exist there but can be added by custom extension. It also says a flagged duplicate is only set to Cancelled, and users can still Retry it. Decide before go-live who may retry one and which layer rejects a repeated invoice number; until then, this screen catches only identical files.\n\nMatching tolerances live in Finance. Microsoft's matching-validation setup page says the applicable price tolerance is looked up when an invoice is compared with its purchase order, and the default legal-entity tolerance is 0 percent. The same page says that with Post invoice with discrepancies set to Allow with warning, an over-tolerance invoice shows a warning but can still post, and suggests that setting where workflows are used to avoid repeated approvals; if you choose it, make sure an approval step sees those invoices. How two-way and three-way matching work as a control is a separate question.\n\n## How are routing and approval configured?\n\nMicrosoft's approval-steps page says a step can go to a role or group, a workflow user, named users, or users in an organizational hierarchy, with a condition setting where hierarchy retrieval stops, and can run always or only when a condition is met. For cost invoices, Microsoft's financial-dimensions page says business unit, department and cost center on the header determine the approver, so those values must be right before routing can be.\n\nThe unhappy path is configured, not emergent:\n\n- **Delegation.** Microsoft's approval-process page lets you allow an approver to assign the document to another user.\n- **Escalation.** The approval-steps page says a document not acted on in the allotted time is overdue and moves along an escalation path, and when the path runs out the system takes an end action automatically.\n- **Timeout.** The approval-process page adds a process-wide time limit after which the system acts on the document, and says it overrides each step's assignment and escalation settings, so use one or the other.\n- **Automatic actions.** The approval-process page lets the system act automatically when conditions are met, and its Test function evaluates a record against those conditions.\n- **Self-approval.** The approval-process page says that by default a submitter included in a step's assignment can approve their own document, and offers Disallow approval by submitter to prevent it. Set it on each workflow, and make sure no final approver usually submits invoices, since the page says such an approver can't complete the approval.\n\nSet every end action and time-limit action to Reject, never Approve, because an approve action lets an invoice nobody reviewed approve itself. Test each automatic-approval condition against real invoices before cutover.\n\n## What does an operator see and do in the processing workspace?\n\nMicrosoft's Invoice capture workspace page describes statuses from Created, Deriving and Validating to Captured, In review, Verified, Transferring, Transferred and Voided: errors hold an invoice in Captured for intervention, In review means it is being corrected in the side-by-side viewer, Verified means reviewed but not transferred, and a touchless invoice waits in Transferring for an automation job in Finance. The same page says Obsolete and Delete permanently remove the captured invoice and its received file. Microsoft's configuration page says business units and security roles let clerks see only invoices assigned to their users, which is how work is divided.\n\nMicrosoft's Vendor invoice center page, a preview feature, groups Finance's pending invoices into stages from capture and import to posting. On that page, operators work statuses including Import failed, Receipt match error (matching reached its maximum attempts), Workflow failed (update and resubmit), Workflow rejected with the approver's reason, and Complete not posted, and a legal-entity filter switches between entities. Microsoft's automation overview says invoices in automated processing cannot be edited until excluded.\n\n## How do exceptions stay inside the system?\n\nGive every way an invoice can fail a configured path:\n\n| When an invoice fails | Path inside the system |\n|---|---|\n| The variance is within tolerance | Microsoft's matching-validation page says Finance shows variance icons when a discrepancy exceeds the applicable tolerance; within it, the invoice continues unflagged. |\n| An operator must decide | It waits in Captured or in the failing Finance stage; after a fix, Microsoft's automation overview lets you restart automated processing for many invoices at once. |\n| The vendor or requester must act | The approver rejects or requests a change, which Microsoft's approval-process page treats as a notifiable event, and the Vendor invoice center keeps the rejection reason. |\n| Master data must change first | Derivation stops. Fix the vendor or entity in Finance and sync it; Microsoft's workspace page says reclassifying reruns derivation and validation. |\n\nSettling an exception by email breaks the record. Microsoft's workspace page says warnings and errors go into each invoice's history log, and the received-files page says you must make sure every invoice file is accounted for to prevent omissions. A fix agreed in email leaves no such record, and every cycle-time and exception measure then counts a clean invoice that was not.\n\n## How does the posting integration work, and how is a failed post caught?\n\nIn the integrated topology, Microsoft's installation page says an invoice-type mapping decides which Finance document the transfer creates. Microsoft's workspace page says a manual transfer runs synchronously and shows an error if invoice generation fails, while a touchless transfer waits for the Transfer invoices from Invoice capture job, which runs hourly by default. Microsoft's Invoice capture overview says the transfer needs the InvoiceCaptureOperator role, placed on the flow user for touchless processing. The workspace page describes no retry path or how a failed touchless transfer is reported, so confirm both in your version.\n\nInside Finance, Microsoft's automation overview says an imported invoice that fails workflow submission is removed from automated processing and, where automatic submission is on, its automation history gives the reason. The same page's parameters decide whether an invoice with a failed receipt match or prepayment still moves on: Check Match product receipt status before workflow submission and Block follow-up automation process in case of prepayment application failure; set both in configuration step 2. For third-party feeds, Microsoft's scanned-documents page lists failed imports from staging and lets a clerk fix one and create the pending invoice.\n\nMicrosoft's Vendor invoice center page lists posting among the tasks users perform but describes no automatic posting step or how a failed post is reported. Decide who posts, how often and who reposts after a fix; run posting simulation first, which the automation overview says runs the posting validations without updating accounts; and confirm in your version where posting failures appear.\n\nAn approved invoice that never reached the ledger is invisible from either system alone. Check two queues daily: the pending-time chart on Microsoft's Invoice capture dashboard, which counts days a captured invoice has not been generated in the ERP system, and the Vendor invoice center's Complete not posted status, which holds invoices that finished approval and await posting. The Vendor invoice center page says the workspace, and so this status, is available only with the (Preview) New vendor invoice center feature enabled and can't coexist with the old Vendor invoice automation workspace.\n\nMicrosoft's Accounts payable postings page says the vendor posting profile sets the summary account used when vendor balances post, and the Invoice capture workspace page says a line's procurement category derives its expense accounting. An illustrative 1,250.00 cost invoice coded to a procurement category and cost centre 200 posts as:\n\n| Account | Debit | Credit |\n|---|---|---|\n| Expense account from the procurement category's accounting, cost centre 200 | 1,250.00 | |\n| Accounts payable trade, from the vendor posting profile | | 1,250.00 |\n\n## What master data must agree with the ledger?\n\nRouting resolves against master data, so configure it only after master data is complete; otherwise invoices route to the wrong approver and the defect appears at production volume. The master data that must agree is:\n\n- **Legal entities and vendors.** Microsoft's configuration page says capture needs legal entities and vendors to classify invoices, legal entities are synced from Finance, and a vendor supplying several legal entities needs an account in each. Microsoft's installation page says vendor changes sync in real time by default, but at larger volumes vendors should be synced manually per legal entity.\n- **Accounts and cost centres.** Microsoft's financial-dimensions page says header dimensions map to Finance at transfer from version 10.0.39, and the workspace page says lookup lists come from Finance at runtime.\n- **Procurement categories and items.** Microsoft's configuration-groups page says cost-invoice lines carry service or procurement category items, which must exist in Finance.\n- **Currencies and charges.** The workspace page says a PO invoice must use the purchase order's currency and a charges code must be assigned before transfer.\n- **Tax codes.** Where imported tax differs from Finance's calculation, establish which is right before correcting the invoice or using the override, which Microsoft's automation overview says replaces the calculated tax with the imported tax, allocated to the linked sales tax codes.\n- **Approval hierarchy.** Microsoft's approval-steps page draws hierarchy-based approvers from the organizational hierarchy, so positions and managers must be current.\n\nWith several entities or currencies, parameterise by entity at design time. Microsoft's channels and configuration-groups pages assign channels and groups per legal entity, and the scanned-documents page says securing the import job by legal entity segregates exception handling. The same page says a data-entity feed lands in the import job's company unless the request names another, so fix each feed's company. Microsoft's matching-validation page says price-total amounts are compared in accounting currency and percentages in transaction currency, so set each entity's tolerance amounts in its accounting currency. For cost invoices without a captured currency, the workspace page's Derive currency code for cost invoice rule takes it from vendor master data. Confirm in your version how routing conditions key to each entity's cost-centre values. A design fixed to one entity has to be rebuilt, not extended.\n\n## How does the captured image stay retrievable from the posted record?\n\nThe image survives only if each hand-off keeps it:\n\n- **In capture.** Microsoft's workspace page says the original can be downloaded from the preview pane. Microsoft's installation page makes transferring the file with the invoice a setting, and the configuration page's Auto invoice cleanup deletes transferred and voided invoices older than 180 days along with the original file, so turn on attachment transfer before cleanup.\n- **In Finance.** Microsoft's scanned-documents page provides an attachment viewer on the invoice journal inquiry for posted invoices, and says a failed import's attachment must be reattached.\n- **Edits to the image.** The same page says highlight, block and annotation changes are saved into the image file, the viewer has no versioning or auditing, and role-based security controls those actions. The page gives the read/write Maintain vendor invoice image privilege to the Maintain vendor invoices duty, held by Accounts payable clerks and managers, so everyone who maintains invoices can alter images unless you change that assignment; give others View vendor invoice image only.\n\n## Who may view, approve, edit and post, and how is each action evidenced?\n\nNIST SP 800-53, a federal security-control catalogue that nongovernmental organizations may use voluntarily, includes controls that also make an approval record usable as evidence: access authorizations that support separation of duties, least privilege, unique identification and authentication of each user, and audit records establishing the event and the identity of those involved. A shared login removes individual accountability for approvals.\n\nConfigure these controls, besides the visibility and self-approval settings above:\n\n- **Segregation.** Microsoft's segregation-of-duties page sets rules for tasks different users must perform, and says you must validate compliance after creating or changing a rule.\n- **Posting.** Name the roles that may post, a user task in Microsoft's Vendor invoice center, and add a segregation rule pairing posting with approval. Confirm in your version what records a post beyond workflow history.\n- **Service identity.** Microsoft's Invoice capture overview puts touchless transfer under a flow user, so keep that identity out of approval roles to keep automated and human actions distinguishable.\n- **Deletion.** Limit Void, Obsolete and Delete to as few people as possible, and review voided invoices before anyone obsoletes them.\n- **Evidence.** Microsoft's automation overview says workflow history is available from the vendor invoice itself. Microsoft's database logging page says logging creates an auditable record of changes to chosen sensitive tables, is not designed for automated batch transactions, and needs a retention plan.\n\n## What does the system report about its own processing?\n\nEach measure counts something narrower than its name suggests:\n\n- **Volume.** Microsoft's Invoice capture dashboard page charts captured invoices by period and per vendor.\n- **Exception cycle time.** The dashboard's days-to-complete chart shows the average days to capture one invoice that needed manual intervention, which covers capture, not approval.\n- **Approver bottlenecks.** Microsoft's Vendor invoice center page shows, for invoices in workflow, the approver, the pending time and the approval due date.\n- **Automation efficiency.** Microsoft's automation overview says Power BI metrics give AP managers insight into automation efficiency.\n\nThe automation overview also says Invoice received date is the starting point for tracking an invoice and defaults to the current date when not entered, so late-keyed invoices understate cycle time. Microsoft's configuration-groups page says the manual-review condition affects the touchless rate, so a permissive configuration can produce the same high rate as a careful one. Neither that page nor the dashboard page says how the rate is calculated or where it appears, so confirm both. Read that rate alongside the review condition, confidence thresholds and automatic-approval conditions behind it.\n\n## How does one invoice travel from mailbox to ledger?\n\nAn illustrative 1,250.00 cost invoice passes through each component in order:\n\n1. The vendor emails a PDF to the AP shared mailbox. The channel supplies the legal entity, and the file filter and checksum duplicate check run on arrival.\n2. The prebuilt model reads it, derivation finds the vendor account from synced vendor data, and the vendor's configuration group supplies mandatory fields and confidence thresholds.\n3. A low-confidence invoice date raises a warning, and because the group requires review on warnings, the invoice stops in Captured.\n4. A clerk corrects the date in the side-by-side viewer, enters cost centre 200 and the line's procurement category, and completes review.\n5. The clerk transfers it, and the invoice-type mapping, set to Vendor invoice rather than Invoice journal for cost invoices, creates a pending vendor invoice with the PDF attached.\n6. Automatic submission, which Microsoft's automation overview describes, sends it to workflow, where a hierarchy step routes it to the cost-centre manager with a three-day limit, escalation to the controller and an end action of Reject.\n7. Once approved it shows as Complete not posted until the designated user posts it, creating the entry above, and the PDF stays viewable from the posted invoice.\n\n## In what order must configuration be finished before the first invoice?\n\nEach step depends on the one before it:\n\n1. Set up ledger master data: legal entities, vendor accounts per entity, vendor posting profiles, financial dimensions, procurement categories and items, charges codes and tax setup.\n2. Set validation in Finance: matching policy, price tolerances and the discrepancy-posting choice, then the automation parameters, including receipt-match and prepayment-failure handling, and enable the (Preview) New vendor invoice center feature.\n3. Build access: the organizational hierarchy, users, security roles and segregation rules, validated for conflicts.\n4. Build approval workflows: assignments, conditions, time limits, escalation end actions and automatic actions, each checked with the Test function.\n5. Enable the Invoice capture for Dynamics 365 Finance feature, which adds Accounts payable > Set up > Invoice capture; then prepare the Power Platform environment and virtual entity, then the Finance-side onboarding of legal entities, attachment transfer and invoice-type mapping, which Microsoft's installation page puts before installation, then install and sync.\n6. Configure capture: model, file filter, processing rules, continuous learning and cleanup, then configuration groups assigned to vendors, then channels with their legal entities, then test that a low-confidence invoice raises its warning.\n7. Test cutover: run posting simulation, import test packages with attachments into a test environment as Microsoft's scanned-documents page describes, and pilot one channel or vendor group before opening the rest.\n\nA pilot confines a misconfigured rule to a small population of invoices.\n\n## What administration does the system need after go-live?\n\nKeep these running after cutover:\n\n- **Extraction upkeep.** Track which vendors keep needing correction, retrain custom models when layouts change, and keep continuous learning on.\n- **Vendor onboarding.** Create each new vendor in Finance and let it sync before its first invoice arrives, then assign its configuration group.\n- **Rule maintenance.** Update tolerances, conditions and escalation paths as people and policies change, and revalidate segregation rules after each change.\n- **Upgrades.** Microsoft's installation page says the system notifies you when a new Invoice capture version is available; test it before upgrading production.\n- **Monitoring.** Check the transfer and posting queues daily and keep the database-log retention plan current.",
  "sources": [
    {
      "id": "REF::1",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/invoice-capture-overview",
      "title": "Invoice capture solution overview",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:48+00:00",
      "sha256": "94ba8e5cb7c655f1c8ab7c11d16af141d0679536308832ccf267f3e702407d8f",
      "supports": [
        "C1",
        "C78",
        "C79"
      ]
    },
    {
      "id": "REF::2",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/install-invoice-capture",
      "title": "Install the Invoice capture solution",
      "publisher": "Microsoft",
      "published": "last updated 07/25/2026",
      "retrieved_at": "2026-09-25T12:28:48+00:00",
      "sha256": "2de7137ff08cbb7f4c7952a78aadf64eeddfd08333b80f2f0c51b6a90ee97230",
      "supports": [
        "C2",
        "C74",
        "C90",
        "C91",
        "C99",
        "C126",
        "C127",
        "C128",
        "C130",
        "C177",
        "C178",
        "C179",
        "C182"
      ]
    },
    {
      "id": "REF::3",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/vendor-invoice-workspace",
      "title": "Vendor invoice center workspace overview",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:49+00:00",
      "sha256": "579105cd3de826e4bd9228f39603523f45cc18fa12d6a3250cbe8f51904840d6",
      "supports": [
        "C4",
        "C58",
        "C59",
        "C60",
        "C61",
        "C62",
        "C63",
        "C64",
        "C65",
        "C120",
        "C163",
        "C164",
        "C165",
        "C166"
      ]
    },
    {
      "id": "REF::4",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/vendor-invoice-automation",
      "title": "Invoice automation for scanned documents",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:49+00:00",
      "sha256": "2e50577ef4e5032ff18c611bfe7b30dbba2e3c1eb78928b513da63e7b915d965",
      "supports": [
        "C5",
        "C12",
        "C83",
        "C84",
        "C97",
        "C102",
        "C103",
        "C104",
        "C105",
        "C106",
        "C129",
        "C171",
        "C172",
        "C185",
        "C186",
        "C187",
        "C188",
        "C189"
      ]
    },
    {
      "id": "REF::5",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/invoice-capture-channel",
      "title": "Manage channels in the Invoice capture solution",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:49+00:00",
      "sha256": "6f172f5bfcf8b904db809e06ac0025a9a9b092376e91e6ceb586037ebe3f7c93",
      "supports": [
        "C6",
        "C7",
        "C8",
        "C9",
        "C11",
        "C135"
      ]
    },
    {
      "id": "REF::6",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/invoice-capture-rec-files",
      "title": "Invoice capture received files",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:50+00:00",
      "sha256": "ecd12858a8dc4a4c092a5633640d4b520d0b8edd5bbdd87e4ece4e238744ff61",
      "supports": [
        "C34",
        "C35",
        "C71",
        "C132",
        "C133",
        "C134",
        "C150",
        "C151"
      ]
    },
    {
      "id": "REF::7",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/config-invoice-capture",
      "title": "Configure the Invoice capture solution",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:50+00:00",
      "sha256": "d044a655864ab92bb8c60f045d731f783f7331828276d69d818df8a91ef22ce7",
      "supports": [
        "C10",
        "C17",
        "C18",
        "C19",
        "C26",
        "C33",
        "C57",
        "C87",
        "C88",
        "C89",
        "C100",
        "C101",
        "C131",
        "C142",
        "C146",
        "C147",
        "C148",
        "C149",
        "C181"
      ]
    },
    {
      "id": "REF::8",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/vendor-portal-invoicing-workspace",
      "title": "Vendor collaboration invoicing workspace",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:50+00:00",
      "sha256": "f7a6d8d8418912fa5d5b5055cee78aa97f1768471480de7298ea35a9cdc3add2",
      "supports": [
        "C13"
      ]
    },
    {
      "id": "REF::9",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/auto-vendr-invc-process",
      "title": "Automated vendor invoicing processes overview",
      "publisher": "Microsoft",
      "published": "last updated 02/10/2026",
      "retrieved_at": "2026-09-25T12:28:51+00:00",
      "sha256": "f127e1a6aa06bc8820228269653af848bc3c3d57fdcc3d3644855e81bb17c86c",
      "supports": [
        "C14",
        "C15",
        "C16",
        "C66",
        "C67",
        "C80",
        "C81",
        "C82",
        "C112",
        "C121",
        "C122",
        "C123",
        "C125",
        "C136",
        "C159",
        "C160",
        "C161",
        "C162",
        "C169",
        "C170",
        "C183",
        "C184"
      ]
    },
    {
      "id": "REF::10",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/invoice-capture-config-group",
      "title": "Invoice capture solution configuration groups",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:51+00:00",
      "sha256": "2ad9aab2c1141fc470c2e5bc57a44867fbbeb9895454573f77ca3755d9db050d",
      "supports": [
        "C20",
        "C21",
        "C22",
        "C23",
        "C30",
        "C31",
        "C96",
        "C124",
        "C137",
        "C139",
        "C140",
        "C141",
        "C168"
      ]
    },
    {
      "id": "REF::11",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/invoice-capture-workspace",
      "title": "Invoice capture solution workspace",
      "publisher": "Microsoft",
      "published": "last updated 12/08/2025",
      "retrieved_at": "2026-09-25T12:28:51+00:00",
      "sha256": "cffc4caaef94368003e7c36bd1e568a6620c88b0a1222914da8f8f8d9bfc44d8",
      "supports": [
        "C3",
        "C24",
        "C25",
        "C27",
        "C28",
        "C29",
        "C32",
        "C53",
        "C54",
        "C55",
        "C56",
        "C69",
        "C70",
        "C75",
        "C76",
        "C77",
        "C93",
        "C94",
        "C95",
        "C98",
        "C138",
        "C143",
        "C144",
        "C145",
        "C155",
        "C156",
        "C157",
        "C167",
        "C176"
      ]
    },
    {
      "id": "REF::12",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/tasks/set-up-accounts-payable-invoice-matching-validation",
      "title": "Set up Accounts payable invoice matching validation",
      "publisher": "Microsoft",
      "published": "last updated 08/04/2025",
      "retrieved_at": "2026-09-25T12:28:52+00:00",
      "sha256": "b388ede73f271529a113191f80bc8bf7eef8e9b3837c31e2e7bde61b6a6b112d",
      "supports": [
        "C36",
        "C37",
        "C38",
        "C39",
        "C158",
        "C173",
        "C174",
        "C175",
        "C180"
      ]
    },
    {
      "id": "REF::13",
      "url": "https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/organization-administration/configure-approval-step-workflow",
      "title": "Configure approval steps in a workflow",
      "publisher": "Microsoft",
      "published": "last updated 03/10/2026",
      "retrieved_at": "2026-09-25T12:28:52+00:00",
      "sha256": "72851e5bea4adebcdf9ac4ae889cc841ccdb7e6f090b9b7c5c9e8d49030e83f3",
      "supports": [
        "C40",
        "C41",
        "C42",
        "C45",
        "C46",
        "C47"
      ]
    },
    {
      "id": "REF::14",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/invoice-capture-dim",
      "title": "Invoice capture financial dimensions",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:52+00:00",
      "sha256": "8cdd65028c5265142bf2a56ce9801b0ffd162255355f756893d90f25f2835dd2",
      "supports": [
        "C43",
        "C92"
      ]
    },
    {
      "id": "REF::15",
      "url": "https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/organization-administration/configure-approval-process-workflow",
      "title": "Configure approval processes in a workflow",
      "publisher": "Microsoft",
      "published": "last updated 03/10/2026",
      "retrieved_at": "2026-09-25T12:28:52+00:00",
      "sha256": "487d0572f4973cf2fb8914d86f9e1500914affddd04a96b2e8e9978acd78c604",
      "supports": [
        "C44",
        "C48",
        "C49",
        "C50",
        "C51",
        "C52",
        "C68",
        "C152",
        "C153",
        "C154"
      ]
    },
    {
      "id": "REF::16",
      "url": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf",
      "title": "Security and Privacy Controls for Information Systems and Organizations, NIST Special Publication 800-53, Revision 5",
      "publisher": "National Institute of Standards and Technology",
      "published": "September 2020, includes updates as of 12-10-2020",
      "retrieved_at": "2026-09-25T12:28:53+00:00",
      "sha256": "fc63bcd61715d0181dd8e85998b1e6201ae3515fc6626102101cab1841e11ec6",
      "supports": [
        "C72",
        "C73",
        "C107",
        "C108",
        "C109",
        "C190",
        "C191",
        "C192"
      ]
    },
    {
      "id": "REF::17",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/invoice-capture-dashboard",
      "title": "Invoice capture solution dashboard",
      "publisher": "Microsoft",
      "published": "last updated 07/28/2026",
      "retrieved_at": "2026-09-25T12:28:56+00:00",
      "sha256": "495ef91f1e2f712bf84539289e90ac4b301ae510e8ea81680d988687d56f49ac",
      "supports": [
        "C85",
        "C116",
        "C117",
        "C118",
        "C119"
      ]
    },
    {
      "id": "REF::18",
      "url": "https://learn.microsoft.com/en-us/dynamics365/finance/general-ledger/accts-payble-posting",
      "title": "Accounts payable postings",
      "publisher": "Microsoft",
      "published": "last updated 06/24/2026",
      "retrieved_at": "2026-09-25T12:28:56+00:00",
      "sha256": "2befdfdb5dea6ea3d1bb6b706a8ce9bb0c97ebb2af68145a970c2d7f743b3f1e",
      "supports": [
        "C86"
      ]
    },
    {
      "id": "REF::19",
      "url": "https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/sysadmin/set-up-segregation-duties",
      "title": "Set up segregation of duties",
      "publisher": "Microsoft",
      "published": "last updated 11/21/2025",
      "retrieved_at": "2026-09-25T12:28:56+00:00",
      "sha256": "4bcd4dfae678189191f1a2767f7401f9943f25e37f5201f2829f7066b7a27479",
      "supports": [
        "C110",
        "C111",
        "C193"
      ]
    },
    {
      "id": "REF::20",
      "url": "https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/configure-manage-database-log",
      "title": "Configure database logging",
      "publisher": "Microsoft",
      "published": "last updated 03/13/2026",
      "retrieved_at": "2026-09-25T12:28:57+00:00",
      "sha256": "b6634791e83ffaa4b9281f2a7104ad0b54df7dffbf4a4add53f33f7e4cb33c4d",
      "supports": [
        "C113",
        "C114",
        "C115"
      ]
    }
  ],
  "related": [
    {
      "question_id": "CG-P1B-001",
      "slug": "what-is-two-way-and-three-way-invoice-matching-in-accounts-payable",
      "display_title": "What is 2-way and 3-way invoice matching in accounts payable, and how do I run it across POs, receiving documents, and vendor invoices?"
    },
    {
      "question_id": "CG-P1B-009",
      "slug": "how-a-small-business-can-manage-and-automate-its-accounts-payable-workflow",
      "display_title": "How should a small business manage and automate its accounts-payable vendor-invoice and document workflow?"
    }
  ],
  "review_class": "consequential",
  "review_class_trigger": "claim_level_review_required",
  "provenance": {
    "author_model": "claude-opus-5-5",
    "reviewer_model": "claude-opus-5-5",
    "review_verdict": "ACCEPT",
    "review_source": "closure",
    "review_verdict_on_sha256": "9b52c7be04f987842267741489c76c49a3c5ec930ed419d47036ad73170cba32",
    "editorial_disposition": "ACCEPT",
    "corrections": 1,
    "approved_by": null,
    "approved_at": null,
    "article_sha256": "9b52c7be04f987842267741489c76c49a3c5ec930ed419d47036ad73170cba32",
    "source_map_sha256": "9fd24ea97f45abb08cec8a4e61a862d14ccda477d1ae89fb68b1622d45abb762",
    "transform_sha256": "75ac871dd2ba383551b870196bd903e6cb55b3f138af60ce02cca16fc13eb1a2"
  },
  "offer": "ask",
  "offer_id": null,
  "sample_target_id": null,
  "datePublished": "2026-09-26T01:29:00Z",
  "reviewed_at": "2026-09-26T01:29:00Z",
  "content_sha": "d8a18f9abe2b47f360de22b1f24104326ba9799dbd3f2a5145cc89875b62faf0",
  "release": "2.7.0",
  "slug_provenance": "minted at first publication",
  "question_text": "How is a vendor-invoice-management system architected, configured and operated to process AP vendor invoices — its components, invoice capture and data extraction, routing and approval flow, the processing workspace and entry points, and its reporting over invoice processing?",
  "jsonld_types": [
    "Article"
  ],
  "related_question_ids": [
    "CG-P1B-001",
    "CG-P1B-009",
    "CG-P1B-FULL-070",
    "CG-P1B-FULL-110",
    "CG-P1B-FULL-111"
  ],
  "aliases": [],
  "alias_provenance": []
}