An EFTPS payment refers to a federal tax payment made through the Electronic Federal Tax Payment System, a free service provided by the U.S. Department of the Treasury. This system enables businesses and individuals to make federal tax payments electronically, ensuring timely and accurate submissions to the Internal Revenue Service (IRS). It functions as a centralized, secure digital conduit for tax obligations, analogous to a specialized, highly secure express lane for financial transfers directly to the government.
Just as a sophisticated logistics network ensures goods reach their destination efficiently and reliably, EFTPS provides a structured pathway for tax funds. Businesses, particularly those with complex payrolls or frequent tax liabilities, rely on EFTPS to meet their obligations without the risks and delays associated with paper checks. Understanding its operational mechanics and architectural implications is crucial for any organization managing financial processes or considering custom software solutions for tax compliance.
Understanding the Electronic Federal Tax Payment System (EFTPS)
The Electronic Federal Tax Payment System (EFTPS) is the primary method for businesses and individuals to pay federal taxes electronically. It was established to streamline tax collection, improve accuracy, and reduce the administrative burden on both taxpayers and the IRS. Rather than sending physical checks, which are prone to postal delays, loss, or manual processing errors, EFTPS facilitates direct debit payments from a designated bank account to the U.S. Treasury.
At its core, EFTPS functions as a secure, web-based portal and phone system that interfaces with the Automated Clearing House (ACH) network, the electronic funds transfer system used by financial institutions in the United States. When a payment is scheduled through EFTPS, it initiates an ACH debit transaction. This debit request is sent to the taxpayer’s bank account on the specified payment date, and the funds are then transferred to the Treasury. This process ensures that payments are recorded with the IRS on the date they are scheduled, even if the actual funds transfer takes a day or two to clear through the banking system.
The creation of EFTPS addressed several critical challenges. Before its widespread adoption, businesses primarily submitted tax payments via paper coupons and checks. This manual system was inefficient, costly to process, and often led to discrepancies or late payments. The transition to EFTPS significantly reduced these issues, offering a more reliable and auditable trail for federal tax obligations. For example, businesses often face penalties for late or incorrect payroll tax deposits; EFTPS provides a mechanism to mitigate these risks by allowing payments to be scheduled well in advance and providing immediate confirmation.
Key stakeholders in the EFTPS ecosystem include the taxpayer (individual or business), the IRS, and the financial institutions involved in the ACH network. Taxpayers are responsible for enrolling in the system, providing accurate banking information, and scheduling payments. The IRS receives the payment data and reconciles it with the taxpayer’s account. Financial institutions execute the ACH transactions, ensuring the secure and timely movement of funds. From an architectural standpoint, EFTPS acts as an abstraction layer over the ACH network, simplifying the complexities of electronic funds transfers for tax purposes and providing a user-friendly interface for scheduling and tracking.
EFTPS differs significantly from other payment methods in its specificity and direct integration with federal tax reporting. Unlike general online banking bill pay services, which might send a check or a generic ACH transfer, EFTPS is purpose-built for federal taxes. It captures specific tax form types, tax periods, and payment due dates, directly linking the payment to the corresponding tax liability. This level of detail is crucial for compliance and accurate record-keeping. While some tax software might offer integrated payment options, these often still route through EFTPS or a similar direct-to-Treasury mechanism in the background. The system provides a level of legal and operational certainty that generic payment platforms cannot, primarily because it is directly managed and endorsed by the U.S. Department of the Treasury.
The Operational Mechanics of EFTPS Payments
Understanding the operational mechanics of EFTPS payments involves recognizing a structured workflow designed for accuracy and compliance. The process typically begins with enrollment, where a taxpayer registers with EFTPS, providing their Employer Identification Number (EIN) or Social Security Number (SSN), banking details, and other necessary information. Once enrolled, the taxpayer receives an EFTPS Personal Identification Number (PIN) and an internet password, establishing secure access to the system. This initial setup is a critical security gate, ensuring that only authorized parties can initiate tax payments.
After enrollment, the core process revolves around scheduling payments. A taxpayer logs into the EFTPS website or uses the phone system to input the payment details: the type of tax (e.g., Form 941 for payroll taxes, Form 1120 for corporate income tax), the tax period, the amount, and the desired payment date. This payment date is crucial, as it is the date the IRS considers the payment received, irrespective of when the funds actually clear the bank. Payments can be scheduled up to 365 days in advance, offering significant flexibility for financial planning and avoiding last-minute rushes.
When a payment is scheduled, EFTPS generates an electronic transaction request. This request, containing all the payment details, is then transmitted through the ACH network. The ACH network is a batch processing system, meaning transactions are collected throughout the day and processed in groups. On the designated payment date, EFTPS initiates an ACH debit entry to the taxpayer’s bank account. The taxpayer’s bank processes this debit, and the funds are then transferred to the U.S. Treasury’s account. This typically takes 1-2 business days for the funds to settle, but as noted, the payment date for IRS purposes is the date scheduled in EFTPS.
EFTPS supports a wide array of federal tax payment types, making it a versatile tool for various entities. This includes:
- Payroll Taxes: Form 941 (Employer’s Quarterly Federal Tax Return), Form 940 (Employer’s Annual Federal Unemployment Tax Return), and Form 943 (Employer’s Annual Federal Tax Return for Agricultural Employees).
- Corporate Income Tax: Form 1120 series.
- Individual Income Tax: Form 1040ES (Estimated Tax for Individuals).
- Excise Taxes: Form 720 (Quarterly Federal Excise Tax Return).
- Trust Fund Recovery Penalty Payments: For individuals held responsible for unpaid trust fund taxes.
Each payment type requires specific codes and identifiers within the EFTPS system to ensure correct allocation. The system’s robustness in handling these diverse tax forms is a testament to its design for comprehensive federal tax compliance.
Error handling and reconciliation are integral to the system’s reliability. If a payment fails (e.g., due to insufficient funds or incorrect bank account information), EFTPS will notify the taxpayer. It is the taxpayer’s responsibility to resolve these issues promptly to avoid penalties. Confirmation numbers are provided for every scheduled payment, serving as proof of initiation. These numbers are vital for auditing and dispute resolution. In a custom software environment, integrating the capture and storage of these confirmation numbers is a critical design requirement for ensuring comprehensive audit trails and facilitating reconciliation processes, often requiring robust software testing to ensure accuracy.
Architectural Considerations for Integrating with EFTPS
Direct programmatic integration with EFTPS through a public API is not available in the traditional sense. Unlike many modern financial services that offer RESTful APIs for direct system-to-system communication, EFTPS primarily operates as a user-facing web portal and phone system. This architectural reality presents specific challenges and opportunities for businesses seeking to automate or streamline their federal tax payment processes within custom software solutions.
Given the lack of a direct API, integration strategies typically revolve around indirect methods, focusing on data preparation, submission automation, and reconciliation. The primary goal is to minimize manual data entry into the EFTPS portal, reduce human error, and ensure timely payments. Here are the common architectural approaches:
-
Manual Data Entry (Baseline):
The simplest, though least efficient, method involves manually inputting payment details into the EFTPS web portal or calling the phone system. While this requires minimal architectural effort, it is prone to errors, time-consuming for large organizations, and lacks an integrated audit trail within a business’s internal systems. This approach is generally suitable only for businesses with very few, infrequent federal tax payments.
-
Automated Data Export for Bulk Processing:
Many businesses with custom ERP or payroll systems generate payment data that could be used for EFTPS. An architectural solution here involves designing the internal system to export payment details in a structured format (e.g., CSV, XML). This exported file can then be used to populate an intermediary system or for manual bulk upload if EFTPS offers such a feature (though this is not a common, widely available public feature for generic users). This approach reduces manual input errors for the data itself, but still requires a human to initiate the upload or entry into EFTPS.
<?php namespace AppServicesTax; use AppModelsTaxPayment; use IlluminateSupportCollection; class EftpsDataExporter { public function exportPayments(Collection $payments): string { $csvData = "EIN,TaxType,TaxPeriod,Amount,PaymentDate "; foreach ($payments as $payment) { $csvData .= sprintf( "%s,%s,%s,%s,%s ", $payment->ein, $payment->tax_type, $payment->tax_period, $payment->amount, $payment->payment_date->format('Y-m-d') ); } return $csvData; } }This PHP example illustrates a basic exporter that generates a CSV string. A more robust solution would handle various tax types and specific EFTPS formatting requirements, which can be quite rigid. The output of such a service would then be manually, or semi-automatically, entered into the EFTPS system.
-
Integration via Third-Party Payroll/Tax Software:
The most common and architecturally sound approach for automation is to integrate with third-party payroll or tax compliance software (e.g., ADP, Gusto, QuickBooks Payroll, or specialized tax compliance platforms). These providers often have established, secure, and audited integrations with EFTPS or similar Treasury direct payment systems. Your custom application would then integrate with these third-party services via their APIs. This shifts the complexity of direct EFTPS interaction to a specialized vendor. For example, a custom Laravel Livewire e-commerce platform handling employee payroll might push payroll data to a service like Gusto, which then manages the EFTPS payments.
This approach involves:
- Defining clear data contracts between your custom system and the third-party API.
- Implementing robust error handling and retry mechanisms for API calls.
- Ensuring secure transmission of sensitive financial data (e.g., using OAuth, encrypted payloads).
- Establishing a reconciliation process to verify payments made by the third-party service against your internal records.
-
Robotic Process Automation (RPA):
For highly customized or legacy systems where API integration with third-party software is not feasible, Robotic Process Automation (RPA) can be considered. RPA bots can be programmed to mimic human interaction with the EFTPS web portal, navigating menus, entering data, and clicking buttons. While this provides a high degree of automation without direct API access, it introduces its own set of architectural challenges:
- Fragility: UI changes on the EFTPS website can break RPA scripts, requiring frequent maintenance.
- Security: RPA bots typically require credentials to be stored and managed securely.
- Scalability: Running many RPA bots can consume significant resources.
- Auditability: Ensuring a clear audit trail for RPA-driven payments requires careful logging and monitoring.
Regardless of the chosen integration strategy, robust security measures, comprehensive logging, and a clear audit trail are paramount. Sensitive data, such as EINs, bank account numbers, and payment amounts, must be handled with the highest level of encryption and access control. Regular reconciliation of internal records with EFTPS confirmations is also critical to ensure compliance and identify any discrepancies promptly. Developers building custom solutions that touch upon such sensitive financial operations must prioritize data integrity and security above all else.
Security and Compliance in EFTPS Operations
Security and compliance are non-negotiable pillars in any financial transaction system, and EFTPS payments are no exception. The U.S. Department of the Treasury designed EFTPS with stringent security protocols to protect sensitive taxpayer data and ensure the integrity of federal tax collections. From an architectural and operational standpoint, understanding these measures is critical for any entity interacting with the system, whether directly or indirectly through custom software.
EFTPS employs multi-factor authentication for user access, typically involving a PIN and an internet password, which are distinct from each other. This layered security helps prevent unauthorized access to taxpayer accounts. Furthermore, all data transmitted to and from the EFTPS website is encrypted using industry-standard protocols (TLS/SSL), safeguarding information during transit. For businesses developing internal systems that generate data for EFTPS, ensuring that their own data handling practices meet or exceed these standards is essential. This includes encrypting data at rest within databases, securing network communications, and implementing robust access controls for employees who handle tax-related information.
Compliance extends beyond just security. It encompasses adherence to federal regulations regarding tax payment deadlines, accuracy of information, and proper record-keeping. EFTPS provides immediate confirmation numbers for scheduled payments, which serve as proof of payment initiation. These confirmation numbers are critical for audit purposes and should be meticulously recorded and stored by any business. Custom software solutions should be designed to automatically capture and archive these confirmations, linking them directly to the corresponding tax liabilities within the business’s financial records. This creates an immutable audit trail, a vital component for demonstrating compliance during an IRS audit.
Data integrity is another key compliance aspect. The accuracy of the Employer Identification Number (EIN), tax type codes, tax period, and payment amount is paramount. A single incorrect digit can lead to a misapplied payment, resulting in penalties, even if the funds were sent on time. Therefore, any custom system preparing data for EFTPS must incorporate rigorous validation routines. This might involve:
- Input Validation: Checking data types, formats, and ranges at the point of entry.
- Cross-referencing: Validating EINs against internal records or external databases if available.
- Checksums/Verification: Implementing internal checks to ensure the data transmitted matches the data intended for payment.
- User Review: Providing a clear summary for review by an authorized user before final submission or export.
Moreover, the principle of least privilege should be applied to internal systems accessing or preparing EFTPS-related data. Only individuals with a legitimate business need should have access to sensitive tax information and the ability to initiate payment processes. Role-based access control (RBAC) within custom applications is a fundamental architectural pattern to enforce this.
Regular security audits and penetration testing of custom financial systems are also crucial. Since EFTPS itself is a highly secure system, the weakest link often lies in the client-side processes or intermediary systems. Identifying and mitigating vulnerabilities in custom software that handles tax data can prevent breaches that could compromise EFTPS access credentials or sensitive payment information. This holistic approach to security and compliance, encompassing both internal systems and external interactions, is indispensable for maintaining financial integrity and avoiding significant legal and monetary penalties.
Automation Strategies for EFTPS Payment Workflows
While direct API integration with EFTPS is not feasible, businesses can implement various automation strategies to streamline their federal tax payment workflows, significantly reducing manual effort and potential for error. These strategies are critical for organizations managing substantial payrolls or complex tax structures, where manual processing becomes unsustainable and risky. The goal is to move from reactive, manual processes to proactive, automated systems that ensure timely and accurate tax deposits.
One foundational strategy involves data consolidation and preparation. Modern businesses often use disparate systems for payroll, accounting, and financial reporting. An effective automation architecture centralizes tax-relevant data from these sources into a single, canonical system or data warehouse. This central repository then becomes the authoritative source for generating EFTPS payment files. For example, a Next.js Amplify application might pull payroll data from a database, combine it with accounting ledger information, and then format it for tax purposes. This step ensures data consistency and reduces the likelihood of discrepancies.
Following data consolidation, the next step is automated data formatting and validation. As discussed, EFTPS requires specific data formats for different tax types. Custom software can be developed to automatically transform raw financial data into the precise structure required for EFTPS submission. This involves mapping internal data fields to EFTPS-specific fields, applying business logic for tax calculations, and performing validation checks to catch errors before submission. This automation can prevent common issues like incorrect EINs, wrong tax period designations, or miscalculated amounts.
interface TaxPaymentData { ein: string; taxType: string; taxPeriod: string; amount: number; paymentDate: string; } function formatForEFTPS(payment: TaxPaymentData): string { // Example: Basic formatting for a hypothetical EFTPS input structure // In a real scenario, this would be highly specific to the tax form and potentially an intermediary system. const formattedAmount = payment.amount.toFixed(2); return `${payment.ein}|${payment.taxType}|${payment.taxPeriod}|${formattedAmount}|${payment.paymentDate}`; } // Example usage: const payrollTax = { ein: '12-3456789', taxType: '941', taxPeriod: '2023Q4', amount: 12500.50, paymentDate: '2024-01-31' }; console.log(formatForEFTPS(payrollTax)); // Output:
Managing EFTPS Payment Confirmations and Reconciliation
Effective management of EFTPS payment confirmations and the subsequent reconciliation process is paramount for financial accuracy and compliance. Once an EFTPS payment is scheduled, the system provides a unique confirmation number. This number is not merely a receipt; it is the official proof that the payment instruction has been received by the U.S. Treasury on the designated payment date. Architecturally, any system interacting with EFTPS, whether directly through manual entry or indirectly via automation, must prioritize the reliable capture and storage of these confirmation numbers.
For businesses utilizing custom software, the integration of confirmation retrieval can take several forms:
Manual Confirmation Logging:
In less automated setups, users manually retrieve the confirmation number from the EFTPS website after scheduling a payment and then input it into the business's internal accounting or ERP system. This method, while simple to implement initially, is error-prone and inefficient for high volumes of payments. It also introduces a potential delay between payment scheduling and internal record updates.
Automated Confirmation Capture (RPA):
If Robotic Process Automation (RPA) is used for payment submission, the same RPA bot can be programmed to extract the confirmation number from the EFTPS website and then input it directly into the company's internal system. This significantly reduces manual effort and improves data consistency. However, as noted before, RPA solutions are susceptible to UI changes on the EFTPS portal, requiring ongoing maintenance.
Third-Party Service Integration:
When using a payroll or tax compliance service that integrates with EFTPS, these services typically provide APIs or reporting features that include EFTPS confirmation numbers. Your custom application would then query these third-party APIs to retrieve the confirmations and update your internal records. This is generally the most robust and scalable approach, as the third-party vendor is responsible for maintaining their integration with EFTPS and handling confirmation retrieval.
Regardless of the capture method, the confirmation number must be linked unequivocally to the specific tax payment transaction within the business's financial records. This creates a complete audit trail, associating the payment amount, tax type, tax period, and payment date with the official IRS confirmation.
Reconciliation is the process of comparing internal financial records with external statements (bank statements, EFTPS payment history) to ensure all transactions match and accounts balance. For EFTPS payments, reconciliation involves several key steps:
- Verify Scheduled vs. Paid: Compare the payments scheduled in your internal system against the payments confirmed by EFTPS.
- Bank Account Debits: Match the EFTPS-initiated debits on your bank statement with the confirmed payments.
- IRS Account Reconciliation: Periodically, businesses should review their IRS tax account transcripts (available through IRS online services) to ensure that all EFTPS payments have been correctly posted to their tax accounts. This is the ultimate verification step, confirming that the IRS has indeed received and applied the payment correctly.
Discrepancies identified during reconciliation, such as a payment confirmed by EFTPS but not debited from the bank, or a payment debited but not showing on the IRS transcript, require immediate investigation. These issues can stem from incorrect banking information, system glitches, or processing errors. A well-designed custom system will include alerting mechanisms to flag such discrepancies, allowing financial teams to address them proactively. For instance, a dashboard in a cross-platform development application could display payment statuses and highlight any unmatched transactions, providing actionable insights for financial controllers.
The architectural design must account for these reconciliation needs by providing robust reporting capabilities, data comparison tools, and the ability to easily access and cross-reference confirmation numbers, payment details, and bank transaction records. This ensures not only compliance but also gives businesses full visibility and control over their federal tax obligations.
Best Practices for Implementing EFTPS Payment Solutions
Implementing any solution involving federal tax payments requires meticulous attention to detail, robust security, and a clear understanding of compliance requirements. For EFTPS payments, several best practices can guide the development and deployment of custom software solutions, ensuring efficiency, accuracy, and reduced risk. These practices are rooted in sound engineering principles and financial operational wisdom.
Firstly, prioritize data validation at every stage. From the initial input of tax data into your internal system to its formatting for EFTPS submission, rigorous validation checks are essential. This includes verifying EINs, tax period formats, tax type codes, and ensuring payment amounts are positive and within expected ranges. Implementing a layered validation strategy, with front-end client-side validation for user feedback and robust back-end server-side validation for data integrity, is a cornerstone. This prevents incorrect data from ever reaching the EFTPS system, thereby avoiding penalties and reconciliation headaches.
Secondly, establish a clear audit trail and immutable logging. Every action related to an EFTPS payment, including who initiated it, when it was scheduled, the exact payment details, and the EFTPS confirmation number, must be logged. This logging should be tamper-proof and easily auditable. Blockchain-like immutable logs or secure database transaction logs are ideal for this purpose. This audit trail is critical for demonstrating compliance to the IRS and for internal financial reconciliation. It answers the 'who, what, when, and how' of every tax payment.
Thirdly, implement robust error handling and notification systems. Payments can fail for various reasons: insufficient funds, incorrect banking details, or system outages. Your custom solution must be designed to gracefully handle these scenarios. This means:
- Clear Error Messages: Providing specific, actionable error messages to users.
- Automated Retries (where appropriate): For transient issues, a limited number of automated retries with exponential backoff can be implemented.
- Proactive Notifications: Alerting relevant stakeholders (e.g., finance team, administrators) immediately when a payment fails or encounters an issue that requires human intervention. This could be via email, SMS, or an internal dashboard notification.
Fourthly, focus on security by design. Given the sensitivity of tax payment data, security must be embedded into the architecture from the outset, not as an afterthought. This involves:
- Encryption: Encrypting all sensitive data, both at rest and in transit.
- Access Control: Implementing granular role-based access control (RBAC) to ensure only authorized personnel can view or modify tax payment information.
- Secure Credential Management: If using RPA or any form of automated interaction that requires EFTPS login credentials, these must be stored in secure vaults (e.g., AWS Secrets Manager, Azure Key Vault) and accessed with strict policies.
- Regular Security Audits: Conducting periodic security assessments, including penetration testing and vulnerability scanning, on the custom application.
Finally, plan for scalability and maintainability. As a business grows, the volume and complexity of tax payments will increase. An EFTPS payment solution should be architected to scale with these demands without requiring a complete overhaul. This involves using modular components, well-defined interfaces, and adhering to coding standards. Regular maintenance, including keeping up with any changes in EFTPS requirements or third-party API specifications, is also crucial. This ensures the solution remains effective and compliant over the long term, adapting to evolving regulatory landscapes and business needs.
Strategic Considerations for Custom EFTPS Solutions
When considering a custom software solution for managing EFTPS payments, businesses face several strategic decisions that extend beyond mere technical implementation. These considerations are critical for aligning the technology investment with broader organizational goals, regulatory compliance, and long-term financial health. As a solutions consultant, the focus shifts to how a custom approach delivers unique value compared to off-the-shelf alternatives.
One primary strategic consideration is the level of customization required for specific business processes. Many off-the-shelf payroll or accounting solutions offer standard EFTPS integration. However, businesses with highly specialized payroll structures, unique tax reporting requirements, or complex internal approval workflows may find these generic solutions insufficient. A custom solution allows for precise alignment with existing operational procedures, minimizing disruption and maximizing efficiency. For example, if a business needs to integrate EFTPS payments with a proprietary project costing system or a multi-entity financial consolidation platform, a custom build might be the only way to achieve seamless data flow and reporting.
Another strategic point is data ownership and control. By building a custom solution, businesses retain full control over their sensitive tax and financial data. This can be a significant advantage for organizations with stringent internal data governance policies or those operating in highly regulated industries. It reduces reliance on third-party vendors for data custody and mitigates risks associated with vendor lock-in or changes in vendor service offerings. The architecture of a custom system can be designed to meet specific data residency requirements, encryption standards, and access protocols that might not be configurable in a generic SaaS product.
The ability to integrate deeply with existing enterprise systems is a major differentiator for custom solutions. For large enterprises, tax payments are not isolated events; they are part of a broader financial ecosystem involving ERP systems, HR platforms, treasury management systems, and business intelligence tools. A custom EFTPS solution can be engineered to integrate seamlessly with these diverse platforms, creating a unified view of financial obligations and payments. This eliminates manual data transfers between systems, reduces reconciliation efforts, and provides real-time visibility into cash flow and tax liabilities. Such deep integration can be challenging with commercial off-the-shelf products, which often have limited integration capabilities.
Furthermore, a strategic custom approach offers the flexibility to adapt to evolving regulatory landscapes. Tax laws and reporting requirements can change, sometimes frequently. A custom-built system, developed with modularity and extensibility in mind, can be updated and reconfigured to accommodate new regulations more rapidly and precisely than waiting for a third-party vendor to release an update. This agility can be a significant competitive advantage, allowing businesses to remain compliant without extensive manual adjustments or workarounds. This is particularly relevant for companies that operate internationally or have complex tax structures that might be affected by various jurisdictions, even if the payment itself is federal U.S. tax.
Finally, the strategic decision often boils down to balancing initial investment against long-term operational efficiency and control. While custom development may entail a higher upfront cost, the long-term benefits of tailored functionality, enhanced security, full data ownership, deep integration, and adaptability can yield a superior return on investment for organizations with complex or evolving federal tax payment needs. It’s about building a sustainable, resilient financial infrastructure that supports growth and minimizes compliance risk, rather than simply fulfilling a payment obligation.
EFTPS payments represent a cornerstone of federal tax compliance for businesses and individuals in the United States. While the system itself provides a secure and efficient mechanism for electronic tax transfers, the architectural decisions surrounding its integration into an organization's financial infrastructure are complex. Whether opting for manual processes, leveraging third-party solutions, or developing highly customized automation, the imperative remains consistent: ensure accuracy, security, and timely submission of tax obligations.
For organizations with intricate financial operations, a custom approach to managing EFTPS workflows offers unparalleled control, deeper integration with existing enterprise systems, and the flexibility to adapt to specific business needs and evolving regulatory requirements. By adhering to best practices in data validation, security, logging, and error handling, businesses can build robust solutions that transform a compliance necessity into a streamlined, low-risk operational process.
Explore our complete Laravel, Basics directory for more guides.
NR Studio builds custom web apps, mobile apps, SaaS platforms, and internal tools for growing businesses. If you're working through a technical decision, feel free to reach out — no commitment required.
References & Further Reading
