Mapping Invoice Approvals After Two Teams Merge
When two teams merge, it's common to encounter confusion in invoice approval workflows, but clear communication and documentation can resolve the issue.

This article is sponsored by LUCI Financial Solutions. Partner content policy
In this article
Two service teams begin operating together in the middle of a billing cycle. An invoice for an ongoing project still names the manager from the old group. The new department lead thinks the project owner already reviewed the work. The person running payments sees an email that says “approved” and cannot tell which decision it covers. An invoice approval map helps the team see who verifies a purchase, who can authorize the expense, and what changes when an item moves from one team to another.
Start with the organization’s current policies and the people who supply and review real invoices. Draw the route one ordinary case takes from receipt through payment. Identify which roles are changing, who is authorized to confirm them, and what to do with items already in progress. Keep the map specific enough that a staff member can find the next approver without guessing from the name on an old email.
Walk an invoice from receipt to release
Ask the teams to describe what they do with an invoice when it arrives. One employee may receive it in a shared mailbox and verify the vendor or project reference. A project lead may confirm that the work described was received. An authorized approver can confirm the scope and amount under the company’s policy. Accounting and payment staff may have separate reviews to perform. Put the roles in sequence and name the source a reviewer checks for each step.
For each job identify the current role, organization or business unit, and the process for confirming authority. Do the same for an alternate when the regular person is absent. A person who knows the project can answer a factual question without being the person authorized to approve payment. Put both names on the map when it helps the employee routing the invoice. Ask the company’s designated policy owner to check that the proposed route matches the organization’s current controls.
GAO’s Green Book describes internal control standards for federal agencies, including control activities and documentation. Its examples can help a company think through responsibility and an auditable record while using its own policies. The company should be able to identify who made each decision and which records were used at the time. GAO Green Book on internal control
Record what moves to the new team and what stays with an earlier record
Use the effective date the company has approved. Identify which transactions begin in the new workflow and which existing files keep their original approvals. Items waiting for a decision may need a defined transition rule. Ask the person responsible for controls to explain where those invoices go. Record one address or system for the receiving team and the route for questions about older invoices. Make sure the receiving role can find the existing review decision without relying on attachments in the outgoing employee’s mailbox.
Check which vendor agreements, cost centers, or approval limits apply after the organizational change. A team name on an invoice may no longer match the finance system. Ask which codes should be used for new records and how staff should identify outstanding transactions that still use earlier codes. Keep the reference the vendor gave you and write down the approved mapping. Let the finance team determine which data changes are necessary and who can make them.
Make one list of open invoices with the work already done and the next decision required. Include the person who can verify receipt, the route for approval, and any issue that remains. If some invoices have been returned to vendors for revision, keep their current status and the reference to the earlier version. Ask which invoices have a payment deadline near the team's transition and assign someone to check them in the first review.
Check what the new system shows to each participant
Have the responsible administrator confirm that each authorized person can see the documents needed for their job. A department head might have the new approval role and still lack access to the purchase reference that explains the invoice. A former approver may see a message generated by the earlier workflow after their responsibility has changed. Show both cases to the people managing the transition so they can verify the current routing and access under the company’s policies. Keep the revised route and the role changes under the appropriate approval process.
Ask each team which reminders it receives and what it does with them. An invoice could continue appearing in an old queue while the current approver is waiting for an alert in the new one. Show the discrepancy in a dated note, then have the system owner confirm where new work will be visible. Find out whether replies from the earlier team should be saved with the invoice record. A successful change means the appropriate person receives the complete source material and the approval is recorded where the payment team expects to see it.
Decide where an exception goes before it becomes urgent
Give the team a path for an unexpected request. A vendor may ask for more than the original estimate, deliver only part of an order, or send an invoice covering several teams. Ask the designated reviewer who can confirm delivery and who can approve a change. For a disputed or revised item, put the current question in the approved system and avoid sending it independently to several people for the same decision. Mark when the ordinary route will resume.
UC Davis’s accounts payable guidance describes checking invoices against approvals, purchase terms, and receipt records. It also discusses distributing duties among different staff members. Its controls are examples from a large institution. Review comparable questions with the people who run your company’s actual payment process. The approval map should show practical responsibility for the current teams and direct exceptions to the role authorized to handle them. UC Davis accounts payable controls
Check what an absence means during the changeover. If the named approver is away, look for the official backup rather than assuming the outgoing manager can make the decision. Give staff the handoff method and the conditions under which the alternate should be contacted. Ask the team who keeps the authorizations current in each system so the written map does not drift away from the actual permissions.
Test invoices that started on either side of the transition
Imagine a vendor was hired by one branch before a merger. The work was finished shortly after the combined team began operating. The project lead can verify the work, but the company has named a different person to authorize the expense under its current controls. The preparer matches the invoice to the project and sends it to the role identified in the transition rule. The reviewer links both the original agreement and the dated approval in the appropriate record.
Use a second case for a new purchase made by the combined team. Test how someone would look up the correct job and find the buying decision. If people still use both sets of project names, give them an approved reference and point them to the right person for questions. Find out who can correct an inaccurate routing label. Run a third example if needed for a missing approver or a revised invoice version. Record wherever a user still has to guess whom to contact.
Ask team members to work from the map without being coached. One person can explain where an invoice goes first, another what evidence they need to verify the work, and another the required approval. Compare their answers and check any disagreement with the company’s finance lead. A short test in the normal workflow can catch a missing role before a real payment is waiting for an answer.
Give the controller the role changes and a review date
LUCI Financial Solutions’ Dallas outsourced controller services describe controller review and financial operations support. If you discuss the team change with the firm, bring the draft route, the approved effective date, and examples of invoices that still need a decision. Ask the adviser which responsibilities and exceptions the business should resolve before it starts routing new invoices. Give them a way to see what staff are actually doing at each step.
After reviewing roles, confirm who owns the final map. Give the affected teams one current copy, the location of the instructions, and a contact for questions. Identify when it will be checked after the first payment cycle. Have an authorized person verify that the written roles align with system access and the approval records the company expects to keep. Update the map when a role or approval changes.
Make the first cycle a check of evidence as well as timing
Select a handful of invoices from the two old teams and the combined one. Ask whether the current file shows the approved version, the work confirmation, and the employee or role that authorized the next action. Check how quickly someone can retrieve the source. If a payment was held because a role was missing, record where the gap started and who will fix the ordinary route. Keep questions about individual invoices open until the relevant staff can confirm them.
When the review is finished, record the approved map and the effective date in the place people use for invoice procedures. Keep the transition instructions available for older items still being resolved. The next employee receiving a bill can locate the right project, confirm which version is under review, and reach the person responsible for the decision.
Find more local business coverage in the Preston Hollow Today partner guides.
Visit LUCI Financial Solutions.
Sources
- GAO Green Book on internal controlgao.gov
- UC Davis accounts payable controlsfinanceandbusiness.ucdavis.edu
- LUCI Financial Solutions’ Dallas outsourced controller serviceslucifinancial.com