August 14, 2023
In an era characterized by digital transformation and lightning-fast transactions, the persistence of paper checks feels like a frustrating anachronism, almost as if you are stepping into a time warp where efficiency and technology don’t exist – “Welcome to the 21st century, where we still act like it’s the 19th.”
For accounts receivable teams, these antiquated payment methods have become more of a hindrance than a convenience. As businesses strive for efficiency, accuracy, and streamlined processes, the cumbersome nature of paper checks stands out as a major obstacle. From delays in processing to increased manual labor and the heightened risk of errors, the continued reliance on paper checks is casting a shadow over the productivity and effectiveness of modern accounts receivable operations.
Dealing with the receipt and processing of checks is a manual operation. In fact, senior AR decision makers estimate that, on average, 11 working hours are spent managing a single invoice, with 78% reporting that up to 15 people are involved in this process! It’s because an AR team dealing with paper check payments need to take scans of all the checks and remittances, where each check needs to be physically scanned or photocopied for record-keeping purposes. Similarly, manually extracting payment and remittance information from check stubs further adds to the processing time. The extracted data then needs to be manually entered into the enterprise resource planning (ERP) system or accounting software. Manual matching of remittances to respective invoices and posting them into the ERP system can be a time-intensive task, especially when dealing with a large volume of checks. These manual processes collectively prolong the payment cycle, resulting in increased Days Sales Outstanding (DSO) and impacting cash flow. It’s no wonder that on average, manual processing of payments is 67% more time-consuming compared to automated payment solutions.
Furthermore, this manual process mandates employees to be physically present at the office to process, where unforeseen circumstances such as illnesses or even vacations can cause setbacks in check and payment processing (especially when you need 15 people for a single invoice!)
The costs associated with processing paper checks are significantly higher compared to digital payment methods. It is estimated that the manual processing costs for US payments are in the range of $12-$30 per invoice, whereas on an annual basis, paper invoice processing can cost over $170K.
Banks often charge fees for services related to check processing, such as lockbox services. These fees can vary based on factors such as the volume of checks and the complexity of the processing requirements. Additionally, manual processes involved in handling checks, such as manual data entry, verification, and reconciliation, require significant manpower and time, which contributes to increased labor costs.
Imagine trying to keep track of the status of hundreds of paper checks and their payment information. The manual nature of the process makes it difficult to determine the precise timestamp when a check is processed, cashed, and updated in the bank database. As a result, businesses may lack real-time visibility into the payment statuses, leading to uncertainty and potential delays in updating their accounts receivable records.
Lost or bounced checks can further complicate the visibility, causing late payments and potentially damaging customer relationships. The lack of insights into a business’s cash flow can be challenging for accounts receivable teams to prioritize and handle payment disputes efficiently, as they may not have a clear picture of the cash inflows and outflows.
63% of firms with highly automated AR processes experience fewer invoicing errors, according to a study by PYMNTs.com. Why? Because of the manual handling and data extraction from paper checks, the likelihood of inaccuracies and discrepancies is increased and inevitable. By performing the manual key-in for capturing remittance information, human errors in data entry can occur, leading to incorrect payment details. Gathering remittance information from different sources, such as emails and web portals, further adds to the complexity and potential for mistakes.
Incorrectly recorded payment details or mismatched remittance data can result in payment disputes or deductions that require significant manual effort, such as calculating line items, communicating with customers, and resolving discrepancies.
Sixty-three percent of respondents report that their organizations faced fraudulent activity via checks. Three-fourths of organizations currently using checks do not plan to discontinue issuing checks, according to the 2023 AFP® Payments Fraud and Control Survey Report. Paper checks pose significant risks in terms of fraud and security breaches, with can include counterfeit checks and forged signatures. Additionally, the level of authorization control is limited, making them vulnerable to fraudulent activities.
If a customer sends a check via postal mail, there is always a possibility of it being intercepted, lost, or stolen during processing and delivery. This increases the risk of financial losses and can potentially harm the trust and confidence of both businesses and their customers. Implementing robust security measures to prevent check fraud, such as watermarking, magnetic ink, and other security features, can be costly and may still not provide foolproof protection.
Simplify your reconciliation process and improve payment transparency by accepting commercial card payments with Boost Intercept, our patented straight-through processing technology.
Ready to start accepting digital payments and increase cash flow? Contact Boost today.
Cookie | Duration | Description |
---|---|---|
__cfruid | session | Cloudflare sets this cookie to identify trusted web traffic. |
ASP.NET_SessionId | session | Issued by Microsoft's ASP.NET Application, this cookie stores session data during a user's website visit. |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
OptanonConsent | 1 year | OneTrust sets this cookie to store details about the site's cookie category and check whether visitors have given or withdrawn consent from the use of each category. |
viewed_cookie_policy | 1 year | The GDPR Cookie Consent plugin sets the cookie to store whether or not the user has consented to use cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
m | 1 year 1 month 4 days | No description available. |
visitor_id492571 | 1 year 1 month 4 days | Description is currently not available. |
visitor_id492571-hash | 1 year 1 month 4 days | Description is currently not available. |
Cookie | Duration | Description |
---|---|---|
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
li_sugr | 3 months | LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
VISITOR_INFO1_LIVE | 5 months 27 days | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
Cookie | Duration | Description |
---|---|---|
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
ai_session | 30 minutes | This is a unique anonymous session identifier cookie set by Microsoft Application Insights software to gather statistical usage and telemetry data for apps built on the Azure cloud platform. |
ai_user | 1 year | Microsoft Azure sets this cookie as a unique user identifier cookie, enabling counting of the number of users accessing the application over time. |
AnalyticsSyncHistory | 1 month | Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie. |
CONSENT | 2 years | YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data. |
ln_or | 1 day | Linkedin sets this cookie to registers statistical data on users' behaviour on the website for internal analytics. |
pardot | past | The pardot cookie is set while the visitor is logged in as a Pardot user. The cookie indicates an active session and is not used for tracking. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
li_gc | 5 months 27 days | Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. |
Cookie | Duration | Description |
---|---|---|
_calendly_session | 21 days | Calendly, a Meeting Schedulers, sets this cookie to allow the meeting scheduler to function within the website and to add events into the visitor’s calendar. |