{
  "question_id": "CG-P1B-FULL-078",
  "slug": "how-three-way-matching-works-for-sales-and-accounts-receivable",
  "display_title": "How does three-way matching apply on the sales and accounts-receivable side?",
  "format": "article-v2",
  "applies_to": {
    "countries": [
      "US"
    ],
    "frameworks": [],
    "tax_year": null,
    "platforms": []
  },
  "general_concept": true,
  "summary": "By analogy, and in reverse. Three-way matching is a payables control for testing a supplier's invoice. On the sales side you write the documents, so before an invoice goes out you tie each line to the customer's order and to a record that the goods shipped or the work was done. That self-check is separate from applying a customer's payment to an open invoice later, and it proves little unless different people handle orders, fulfillment and invoicing.",
  "body": "## Is three-way matching a sales-side term at all?\n\nAccountingTools' three-way matching definition describes a payment verification technique for making sure a supplier invoice is valid before it is paid, by matching it to the buyer's purchase order and receiving report. The buyer tests a claim someone else wrote.\n\nOn the sales side you are the supplier, so the direction reverses: you check your own claim before you make it. That definition covers only supplier invoices; AccountingTools' billing-process article puts the sales-side checks in the billing clerk's review, which starts from the daily shipping log and confirms each shipment is ready for billing. Treat \"three-way\" here as an analogy: you hold no purchase order or receiving report of your own. The payables version belongs to the accounts-payable matching question.\n\n## What are the sales-side counterparts of the three documents?\n\nEach payables document has a counterpart, but who writes it changes:\n\n| Payables document | Sales-side counterpart | Who writes it |\n|---|---|---|\n| Purchase order | The customer's purchase order or contract, entered as your sales order | The customer writes the order; your order desk, the sales order |\n| Receiving report | Packing slip, shipping log, carrier proof of delivery, signed receipt, approved time records or milestone sign-off | Your staff, a carrier or the customer |\n| Supplier invoice | Your draft sales invoice | You |\n\nAccountingTools' sales-order definition describes the sales order as the seller's internal document, translating the customer's purchase order into the seller's format. The customer matches your invoice against its own order, so first have someone other than the person who keyed the sales order check it against the customer's purchase order or contract: items, units, quantities, prices, discounts, terms and PO number.\n\nWhether a tie is possible depends on your fulfillment record:\n\n| If your fulfillment record is | Then |\n|---|---|\n| A shipping document for goods that left your premises | Compare order, shipment and draft invoice line by line |\n| Acceptance, time or completion evidence for services | That record stands in for the shipping document (see the billing models below) |\n| Nothing kept apart from the order | No tie exists: the invoice only restates the order. Create a dated fulfillment record before billing |\n\n## What does the tie compare, and at what level?\n\nAt the header, the draft invoice must agree with the order on customer, addresses, the customer's PO or contract number and payment terms. Then check each line:\n\n- **Item and unit.** The item or service and its unit of measure are the ones ordered and the ones shipped or performed.\n- **Quantity.** The quantity billed equals the quantity shipped or performed, up to the quantity ordered; bill more only where the customer has agreed in writing to keep the excess.\n- **Price and discount.** The unit price and any discount are the ones on the order.\n- **Extension.** Quantity times price is right on every line.\n\nWork line by line, not on totals: a short-shipped line and an overpriced line can offset each other and leave the totals equal.\n\nAccountingTools' billing-process article adds three checks: prices approved by order entry, or matched to the official price list with any variance approved; freight added unless the order is flagged prepaid or customer pickup; and the customer's sales tax code confirmed.\n\n## What must the tie confirm, and what does issuing the invoice commit you to?\n\nBefore release, the tie must confirm four things:\n\n- **An accepted order.** A customer order or contract supports every line, and credit has been approved.\n- **Fulfillment.** Each line billed was shipped or performed, shown by a record other than the order.\n- **Agreed price and terms.** Prices, discounts and terms are the ones the customer accepted, or an approved variance the customer agreed to.\n- **One bill per delivery.** Every shipment or period of work is billed exactly once.\n\nWhere the contract provides for billing before you perform, as with a retainer, subscription or deposit, its billing schedule replaces the fulfillment test.\n\nDelivery evidence matters because revenue follows control. ASC 606, as quoted in the objective-and-background section of Deloitte's Revenue Recognition Roadmap, recognizes revenue when, or as, a promised good or service is transferred, which happens when, or as, the customer obtains control. The Roadmap's point-in-time section quotes the standard's indicators of control, including physical possession and customer acceptance, and its caution that possession may not coincide with control: under some consignment and repurchase arrangements the customer holds goods the seller controls, and under some bill-and-hold arrangements the reverse. Take such arrangements to your accountant before invoicing them as a sale.\n\nPosting the invoice records a balance on the customer's account; Microsoft's Business Central page on sales orders, for example, says posting creates customer ledger entries. The Roadmap's section on receivables quotes ASC 606: that balance is a receivable only if your right to payment is unconditional, meaning only the passage of time is required before payment is due. An invoice for goods not yet delivered, under a contract that makes payment due on delivery, records a balance the customer can dispute and your books cannot support. Where you bill before you perform, the Roadmap's section on contract liabilities quotes ASC 606: if the customer has paid, or your right to the payment is unconditional, before you transfer the goods or services, the contract is presented as a contract liability when payment is made or due, whichever is earlier, and under the revenue rule above the amount becomes revenue as you perform. If your system posted an advance bill straight to sales, ask your accountant how to carry it.\n\nThese are U.S. GAAP rules: ASC 606 sits in FASB's Accounting Standards Codification, which FASB's Update 2014-09 calls the source of authoritative GAAP for nongovernmental entities. On another basis of accounting, ask your accountant how an advance bill is carried; the pre-billing tie is unchanged.\n\n## How does one customer order run through to the invoice?\n\nLakeside Bistro sends purchase order 4471 for three lines, net 30, freight prepaid. Your order desk enters sales order SO-1182, a second person checks it against PO 4471, and someone outside sales approves credit. The warehouse ships, records packing slip PS-2210 and gets the receiver's signature. Billing starts from PS-2210 and pulls SO-1182; the billing screen pre-fills a draft invoice from the order. The header agrees. One line does not:\n\n| Line | Order price | Ordered | Shipped | Draft invoice | Issued invoice | Billed, before tax |\n|---|---|---|---|---|---|---|\n| Paper cups, case | 32.00 | 40 | 40 | 40 | 40 | 1,280.00 |\n| Cup lids, case | 18.50 | 20 | 12 | 20 | 12 | 222.00 |\n| Napkins, carton | 24.00 | 10 | 10 | 10 | 10 | 240.00 |\n| Total | | | | | | 1,742.00 |\n\nThe draft came from the order, so it billed all 20 cases of lids; the packing slip shows 12, with 8 back-ordered. The clerk corrects the line to 12 before release and leaves 8 open on SO-1182. Sent as drafted, the invoice would have billed 148.00 for lids never received and failed the bistro's receiving match. The 8 cases go on a second invoice, citing PO 4471 and their own packing slip, when they ship; the two invoices total the order's 1,890.00.\n\n## How are the sales-side exceptions resolved?\n\nMost exceptions are settled before billing:\n\n| Exception | What may be billed, and how it is resolved |\n|---|---|\n| Partial shipment | Bill only the quantity shipped; the rest of the line stays open on the order |\n| Back order | Bill those units only when they ship, citing their own shipment and the same customer order |\n| Over-shipment | Bill the ordered quantity unless the customer agrees in writing to keep and pay for the extras; otherwise arrange their return |\n| Price or discount different from the order | Bill the order price unless a new price is approved internally and agreed with the customer |\n| Billing ahead of delivery | Hold the invoice until fulfillment evidence exists, unless the contract provides for advance billing (see what issuing the invoice commits you to) |\n\nOther exceptions surface after the invoice is out: the customer rejects it, pays less, or reports goods short or damaged. Check the disputed line against your fulfillment evidence. If your invoice was wrong, correct it with a revised invoice or a credit memo; AccountingTools' three-way matching definition notes that a failed buyer's match may end in either. If the customer's records are wrong, send your delivery or acceptance evidence. If goods arrived damaged, the invoice and the customer's records can both be right: agree the remedy with the customer, and issue any credit as a credit memo.\n\n## What stands in for the delivery document for services, milestones, retainers and subscriptions?\n\nWithout shipments, the fulfillment leg changes shape:\n\n| Billing model | What the billing rests on |\n|---|---|\n| Hourly or time and materials | Approved time records for the billed period; AccountingTools' missed-billings article recommends locking timekeeping records once submitted, so later changes go to billing |\n| Milestone or progress billing | Documented completion of the milestone, with the customer's sign-off where the contract requires acceptance |\n| Retainer or subscription billed in advance | The contract and its billing schedule; the invoice precedes the work (see what issuing the invoice commits you to) |\n\n## Who should accept the order, confirm fulfillment and issue the invoice?\n\nPayables matching draws its force from independence: supplier, purchasing and receiving each produce one document. On the sales side your business writes the sales order and the invoice, and usually the fulfillment record; only a carrier's records and the customer's own signed receipt or sign-off come from outside, which is why the one-person control below relies on them. If one person can do all three, that person can make the documents agree, so the tie still catches slips but proves only that the business agrees with itself.\n\nCOSO's executive summary of its Internal Control — Integrated Framework says segregation of duties is typically built into control activities and that, where segregation is not practical, management selects and develops alternative control activities. It prescribes no billing split; here is one that applies the principle:\n\n- **Order acceptance.** Order entry records the order at agreed prices, and someone outside sales approves credit, a role AccountingTools' sales-order definition gives the credit department.\n- **Fulfillment confirmation.** Whoever ships or performs the work records it, and the biller cannot create or change that record.\n- **Invoicing.** The biller works from the fulfillment record, not the order, and cannot change approved prices.\n- **Review.** Someone outside all three roles checks both directions: on a set schedule, that every shipment was billed; before release, that every invoice line is backed by a shipment or performance record.\n\nAccountingTools' missed-billings article gives the first check, a second person confirming every shipping notification was billed, as the fix when shipping paperwork reaches billing disorganized; the second, run before release, is what stops billing ahead of delivery.\n\nWhere one person does all three jobs, the alternative control must rest on evidence that reaches the reviewer without passing through that person. Before release, the owner, or someone who neither bills nor records fulfillment, checks each invoice against carrier tracking looked up directly, the customer's acceptance sent to the reviewer, or the owner's own check of what left or what was done. On a set schedule, the reviewer also works back from the carrier's statement, a stock count or customer sign-offs to the invoices issued, to find deliveries never billed.\n\n## How do you run the tie in a system, and by hand?\n\nCheck first whether your system invoices from the order or from a recorded delivery. Microsoft's Business Central page on selling with sales orders, last updated April 7, 2026, describes a delivery-based design: you cannot invoice from the Sales Orders page for something not yet shipped, unless you ship and invoice in one posting, so the rule shows a shipment was recorded, not who recorded it. The page also allows invoicing without a shipment from the Sales Invoices page or with Make Invoice on a sales quote; put those invoices and combined ship-and-invoice postings on the reviewer's list. Partial shipments are invoiced by setting quantities to ship and invoice on each line, unless the order's Shipping Advice is Complete, which blocks partial shipments.\n\nBy hand, the tie needs a numbered customer order, a numbered and dated fulfillment record, and an invoice citing both. Run it in this order:\n\n1. Start from the day's fulfillment records, not from open orders.\n2. Pull the sales order for each record and compare the header and every line.\n3. Draft the invoice at the quantities fulfilled and the order prices, resolving any exception first.\n4. Write the invoice number on the fulfillment record, so the reviewer can see what is still unbilled.\n\n## How is the pre-billing tie different from applying a customer's payment?\n\nThe two ties answer different questions:\n\n| Aspect | Before the invoice is issued | After the invoice is issued |\n|---|---|---|\n| Documents | Order, fulfillment record, draft invoice | Customer's remittance, open invoice |\n| Question answered | Should we bill this, and for how much? | Which open invoice does this payment settle? |\n| What it catches | Unshipped, short-shipped or mispriced lines, before the customer sees them | Short payments and disputes, after the fact |\n\nMicrosoft's Business Central page on reconciling customer payments describes applying a received payment to close the customer's open entries. That tie cannot reveal a wrong invoice until the customer short-pays or disputes it, so if it is your only matching, nothing checks an invoice before it goes out. Recording part, combined and excess payments has its own question.\n\n## What does a customer's own matching need from your invoice?\n\nA customer running three-way matching compares your invoice with its purchase order, which states the quantity and price it agreed to buy, and its receiving documentation, which confirms the goods arrived in the correct quantity and good condition, as AccountingTools' three-way matching definition describes. AccountingTools' billing-process article counts rejected invoices and missing purchase order numbers among signs of a failing billing process. Your invoice should therefore carry:\n\n- The customer's PO number, and its line numbers if it uses them\n- The item descriptions and units of measure used on the order\n- The quantity shipped, which is what its receiving record shows\n- The order's unit price and the extended amount\n- Your shipment reference and ship date\n\nFederal contracts that include the Prompt Payment clause (FAR 52.232-25) set a formal test: a proper invoice must include every item listed in paragraphs (a)(3)(i) through (x) of the clause, and one that does not is returned. Besides the contract or order number with line item numbers; description, quantity, unit of measure, unit and extended price; shipping and payment terms such as shipment number and date; and any documentation the contract requires, the list includes your name and address, the invoice date and number, the name and address of your official to whom payment is sent, and the person to notify about a defective invoice. Check the full list in the clause before invoicing a federal customer.\n\nBusiness Central's sales-order page describes an External Document No. field for the customer's own order number, with a setup option that blocks posting an invoice without one. Other invoice content and numbering are covered in the question on customer invoice content.",
  "sources": [
    {
      "id": "REF::1",
      "url": "https://www.accountingtools.com/articles/what-is-three-way-matching.html",
      "title": "Three-way matching definition",
      "publisher": "AccountingTools (Steven Bragg)",
      "published": "May 14, 2026 (date shown on page)",
      "retrieved_at": "2026-09-25T10:35:07+00:00",
      "sha256": "f976e8aed5e52108db516e678359b34cbfc68f19400d8e1425f80d76cd9d3808",
      "supports": [
        "C1",
        "C2",
        "C24",
        "C56",
        "C41",
        "C42"
      ]
    },
    {
      "id": "REF::2",
      "url": "https://www.accountingtools.com/articles/billing-procedure",
      "title": "The billing process",
      "publisher": "AccountingTools (Steven Bragg)",
      "published": "June 08, 2026 (date shown on page)",
      "retrieved_at": "2026-09-25T10:35:08+00:00",
      "sha256": "670fca81cb57a49386dd7bb0044c9dd1b2ce386bb1e02f7c4084bee99a5cb867",
      "supports": [
        "C3",
        "C4",
        "C7",
        "C8",
        "C9",
        "C10",
        "C43"
      ]
    },
    {
      "id": "REF::3",
      "url": "https://www.accountingtools.com/articles/sales-order",
      "title": "Sales order definition",
      "publisher": "AccountingTools (Steven Bragg)",
      "published": "July 29, 2026 (date shown on page)",
      "retrieved_at": "2026-09-25T10:35:09+00:00",
      "sha256": "65d6366004a3e2dbdccd2394b9d70ae23516abe96364d866d80034b89f419d38",
      "supports": [
        "C5",
        "C6",
        "C31"
      ]
    },
    {
      "id": "REF::4",
      "url": "https://dart.deloitte.com/USDART/home/codification/revenue/asc606-10/roadmap-revenue-recognition/chapter-8-step-5-determine-when/8-1-objective-background",
      "title": "Revenue Recognition Roadmap, 8.1 Objective and Background",
      "publisher": "Deloitte Development LLC (Deloitte Accounting Research Tool, DART)",
      "published": "undated section page (the Roadmap's landing page shows a November 2025 edition); quotes current ASC 606 text",
      "retrieved_at": "2026-09-25T10:35:09+00:00",
      "sha256": "104be002752913d6a16800e7bb317d62638041648888ce84a41214bd459242c2",
      "supports": [
        "C11",
        "C12"
      ]
    },
    {
      "id": "REF::5",
      "url": "https://dart.deloitte.com/USDART/home/codification/revenue/asc606-10/roadmap-revenue-recognition/chapter-8-step-5-determine-when/8-6-revenue-recognized-a-point",
      "title": "Revenue Recognition Roadmap, 8.6 Revenue Recognized at a Point in Time",
      "publisher": "Deloitte Development LLC (Deloitte Accounting Research Tool, DART)",
      "published": "undated section page (the Roadmap's landing page shows a November 2025 edition); quotes current ASC 606 text",
      "retrieved_at": "2026-09-25T10:35:10+00:00",
      "sha256": "c89790bf916157d6ba1ff0361ad6c7895809b4a3daf702569686144d02fc3975",
      "supports": [
        "C13",
        "C14",
        "C15",
        "C16",
        "C17"
      ]
    },
    {
      "id": "REF::6",
      "url": "https://learn.microsoft.com/en-us/dynamics365/business-central/sales-how-sell-products",
      "title": "Create a customer sales order and sell products - Business Central",
      "publisher": "Microsoft",
      "published": "last updated 2026-04-07 (en-us)",
      "retrieved_at": "2026-09-25T10:35:11+00:00",
      "sha256": "d2c32caae4ca178d8ab41c9ee0e06ecbd819b3064f727e5aa3302a079e77cc46",
      "supports": [
        "C18",
        "C34",
        "C35",
        "C36",
        "C37",
        "C38",
        "C39",
        "C48",
        "C49"
      ]
    },
    {
      "id": "REF::7",
      "url": "https://dart.deloitte.com/USDART/home/codification/revenue/asc606-10/roadmap-revenue-recognition/chapter-14-presentation/14-5-receivables",
      "title": "Revenue Recognition Roadmap, 14.5 Receivables",
      "publisher": "Deloitte Development LLC (Deloitte Accounting Research Tool, DART)",
      "published": "undated section page (the Roadmap's landing page shows a November 2025 edition); quotes current ASC 606-10-45-4 text, which refers to Subtopic 326-20",
      "retrieved_at": "2026-09-25T10:35:11+00:00",
      "sha256": "b6b6ab558bf7c6d5f4cb22f43d557bb993557072832a37034a81c9a04353cd60",
      "supports": [
        "C19",
        "C20"
      ]
    },
    {
      "id": "REF::8",
      "url": "https://dart.deloitte.com/USDART/home/codification/revenue/asc606-10/roadmap-revenue-recognition/chapter-14-presentation/14-2-contract-liabilities",
      "title": "Revenue Recognition Roadmap, 14.2 Contract Liabilities",
      "publisher": "Deloitte Development LLC (Deloitte Accounting Research Tool, DART)",
      "published": "undated section page (the Roadmap's landing page shows a November 2025 edition); quotes current ASC 606-10-45-2 text",
      "retrieved_at": "2026-09-25T10:35:12+00:00",
      "sha256": "4d44559e0bf79ac88b14611ea7626fe5314685475bb3de15f15580e331e6f7c4",
      "supports": [
        "C21"
      ]
    },
    {
      "id": "REF::9",
      "url": "https://storage.fasb.org/ASU%202014-09_Section%20A.pdf",
      "title": "Accounting Standards Update No. 2014-09, Revenue from Contracts with Customers (Topic 606), Section A",
      "publisher": "Financial Accounting Standards Board",
      "published": "May 2014",
      "retrieved_at": "2026-09-25T10:35:13+00:00",
      "sha256": "0fa5f4241d383af7a7ea1ab24b742797c598c7967b133e21e09d9c3d92166848",
      "supports": [
        "C22",
        "C23"
      ]
    },
    {
      "id": "REF::10",
      "url": "https://www.accountingtools.com/articles/avoid-missed-billings",
      "title": "How to avoid missed billings",
      "publisher": "AccountingTools (Steven Bragg)",
      "published": "July 17, 2026 (date shown on page)",
      "retrieved_at": "2026-09-25T10:35:14+00:00",
      "sha256": "975e3126f0d444d2bb14cc503ea1ba8beb9a5a5f8e612698b0d103b0b9e2f47e",
      "supports": [
        "C25",
        "C32",
        "C33"
      ]
    },
    {
      "id": "REF::11",
      "url": "https://www.coso.org/_files/ugd/3059fc_1df7d5dd38074006bce8fdf621a942cf.pdf",
      "title": "Internal Control — Integrated Framework: Executive Summary",
      "publisher": "Committee of Sponsoring Organizations of the Treadway Commission (COSO)",
      "published": "May 2013",
      "retrieved_at": "2026-09-25T10:35:15+00:00",
      "sha256": "488d8ddec9ed24b61aea05374e255824fe7d181ea861b9cbedc63c5e2675fd59",
      "supports": [
        "C28",
        "C29",
        "C30"
      ]
    },
    {
      "id": "REF::12",
      "url": "https://learn.microsoft.com/en-us/dynamics365/business-central/receivables-how-apply-sales-transactions-manually",
      "title": "Reconcile customer payments with the cash receipt journal or from customer ledger entries - Business Central",
      "publisher": "Microsoft",
      "published": "last updated 2025-08-21 (en-us, as shown in the pinned snapshot)",
      "retrieved_at": "2026-09-25T10:35:15+00:00",
      "sha256": "7938e46f5540c3125914e0b86b717c42e39b985d8e096629a2226fb67b2e8f94",
      "supports": [
        "C40"
      ]
    },
    {
      "id": "REF::13",
      "url": "https://www.acquisition.gov/far/52.232-25",
      "title": "52.232-25 Prompt Payment",
      "publisher": "Acquisition.gov (Federal Acquisition Regulation)",
      "published": "Jan 2017 (clause date)",
      "retrieved_at": "2026-09-25T10:35:16+00:00",
      "sha256": "120940994362a70e07aa66077c1ee5bf09aaa93ac6a3345eb895cfba1b5ae6ac",
      "supports": [
        "C50",
        "C51",
        "C44",
        "C45",
        "C46",
        "C47",
        "C52",
        "C53",
        "C54",
        "C55"
      ]
    }
  ],
  "related": [
    {
      "question_id": "CG-MCE-029",
      "slug": "what-has-to-be-on-a-customer-invoice-for-it-to-work-as-a-business-record-and-how",
      "display_title": "What has to be on a customer invoice for it to work as a business record, and how should I number and issue invoices?"
    },
    {
      "question_id": "CG-MCE-030",
      "slug": "a-customer-paid-part-of-an-invoice-or-sent-one-payment-covering-several-invoices",
      "display_title": "A customer paid part of an invoice, or sent one payment covering several invoices, or paid too much — how do I record it against their account?"
    },
    {
      "question_id": "CG-MCE-032",
      "slug": "my-accounts-receivable-shows-invoices-as-unpaid-that-customers-already-paid-how",
      "display_title": "My accounts receivable shows invoices as unpaid that customers already paid — how do I find and fix the wrong balances?"
    },
    {
      "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-FULL-129",
      "slug": "how-to-reconcile-invoices-to-their-supporting-records",
      "display_title": "How do I reconcile invoices — tying invoice records to their supporting or corresponding records?"
    }
  ],
  "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": "21143b732da4d68a877ac6b107c3c66593e2b7e9a3fa64f5715fe05ad12ef906",
    "editorial_disposition": "ACCEPT",
    "corrections": 1,
    "approved_by": null,
    "approved_at": null,
    "article_sha256": "21143b732da4d68a877ac6b107c3c66593e2b7e9a3fa64f5715fe05ad12ef906",
    "source_map_sha256": "ce506866baaccbfe83f2acad87e691143de385e9bfffe63d195a41507dd1cde6",
    "transform_sha256": "e0d1777c4ea8c300effeeffad931d6c8e258c19fcb4672a06acd037efcc81f4a"
  },
  "offer": "ask",
  "offer_id": null,
  "sample_target_id": null,
  "datePublished": "2026-09-26T01:29:00Z",
  "reviewed_at": "2026-09-26T01:29:00Z",
  "content_sha": "aba4078b4118cddc566872257e3644fe018ee26b00b05ef615b3301ed707c67e",
  "release": "2.7.0",
  "slug_provenance": "minted at first publication",
  "question_text": "How does three-way matching apply on the sales and accounts-receivable side?",
  "jsonld_types": [
    "Article"
  ],
  "related_question_ids": [
    "CG-MCE-029",
    "CG-MCE-030",
    "CG-MCE-032",
    "CG-P1B-001",
    "CG-P1B-FULL-129"
  ],
  "aliases": [],
  "alias_provenance": []
}