FAQ

DCA only collects non-sensitive operational data from printers. This includes:

• Serial number
• Model, MAC address and IP address
• Meter Reads
  
• Consumable levels
• Error messages displayed by the device

It does not collect user data, print jobs, document names, or printer settings. All data is read-only via SNMP and fully auditable.

Yes. The built in Noetics DCA agent is open source, and its full source code is included with every installation. This makes it 100% auditable. Users can extract the code by renaming the executable (e.g., dca.exe) to a .zip file and decompressing it, allowing full inspection of how the agent operates and what data it transmits.

• Install or extract the DCA .msi package.
• Locate the executable file (dca.exe or monitor-silent.exe).
• Rename it to .zip (e.g., dca.exe.zip).
• Decompress it using any standard archive tool.
• This will give you access to the agent’s source code and internal structure.

The Noetics DCA is not installed as a traditional Windows service and does not run continuously in the background. Instead, it operates as a Scheduled Task that launches only when needed—either manually or based on a configured schedule. This approach improves system performance and security by ensuring the DCA does not remain active in memory or consume resources unnecessarily. You won’t find it listed under Windows Services; it runs only when triggered, then shuts down automatically. 

The Noetics DCA transmits data over standard internet ports using either HTTPS (port 443) or HTTP (port 80), based on your configuration. HTTPS provides secure, encrypted transmission, while HTTP offers full transparency—making it ideal for auditing. When configured to use HTTP, all data sent by the DCA is readable in plain text, allowing you to inspect exactly what information is being transmitted, where it’s going, and how it's structured. This ensures full visibility and control over the communication process.

The Noetics DCA requires no inbound network access. It only uses outbound ports 80 (HTTP) and 443 (HTTPS) to transmit data—both of which are standard and typically already open in most firewall configurations. All collected data is securely sent to a fixed, public Noetics processing server over the internet. The destination server uses a known, static IP address, making the DCA’s network behavior predictable, controllable, and fully auditable.

Yes. The Noetics DCA is designed to meet stringent security and compliance requirements, including:

• HIPAA (Healthcare)
• SOX (Financial transparency)
• GLBA (Financial data privacy)
• FISMA (Federal information security)
• ENISA (EU cybersecurity directives)
• RFCs for communication and data transmission protocols

This makes it suitable for use in healthcare, finance, military, and government sectors.

No. The Noetics DCA is a read-only, non-invasive tool. It does not require printer configuration changes, does not install as a service, and does not push drivers or updates. It only uses SNMP in read-only mode to gather data.

If a list of IP addresses is not provided, the DCA performs automatic discovery across the network using SNMP. This process is designed to be slow and efficient to avoid consuming bandwidth or disrupting devices. Discovery can be accelerated if printer IPs are known and preloaded.

Yes. The DCA supports complex network topologies, including segmented VLANs and WANs. It can be deployed on central or subnet-specific servers, and multiple DCAcan be used to cover different network segments. It works without requiring changes to network routes, printer ports, or firewall settings.

Once DCAs are imported and linked to contracts, Noetics automatically begins scanning the customer’s network. Discovered printers are added to the associated PILOT contract, where they start reporting data. From there, you can review and move valid machines to an ENTERPRISE contract to activate billing and service workflows.

Only for Noetics native DCA. After importing DCA records via Excel, you can select all the created records in MPS > Devices > DCAs and use the “Request License” action to generate licenses in bulk.

When delivering equipment, Noetics may ask if you want to send DCA installation instructions to the customer. Click "Yes" only if you're using the Noetics DCA, which will assign a license and send the download link automatically.

If you're using another DCA (like EKM or PrintFleet), always click "No", then go to MPS > DCAs and manually create a DCA record linked to the customer contract.

In Noetics, a contract is a structured digital record that links a customer to a group of machines and determines how those machines are monitored, billed, and serviced. Contracts are created under MPS > Contracts and contain fields for contract profile, duration in months, tags, sales channel, and customer assignment. Every contract starts in PILOT mode, which serves as a staging area where machines discovered by a DCA are collected for review. PILOT contracts are safe zones: they do not generate invoices, service alerts, or consumable orders.

Once a machine is confirmed as actively managed, the contract is duplicated and converted to ENTERPRISE. This transition enables the full billing lifecycle, including invoice generation, alerting, and consumable automation. The standard naming convention appends “-ENT” to the new contract for clarity. Contracts can be associated with one or more DCAs, which push discovered devices into the PILOT automatically. This two-phase model allows teams to separate discovery from billing, ensuring that only validated machines are included in active service and invoicing. Changing the contract type directly affects system behavior, making contracts a central and dynamic control point for service delivery.

In Noetics, a machine refers to a structured record representing a device on a service contract.  Machines are the core units around which metering, invoicing, service dispatch, consumable tracking, and maintenance billing are built. Each machine record typically includes:

• Serial Number – the unique ID of the device
• Model – The actual model of the machine. 
• Status – e.g., Installed, Not Installed
• Class – NET, NETLESS, or LOCAL, depending on monitoring setup

Machines also hold additional fields like location, key operator, billing rates, maintenance and lease charges (if applicable), and contract associations.

• INSTALLED: Machine is active and will trigger billing, consumables, and alerts.
• NOT INSTALLED: Machine is visible but will not trigger service actions. Used for onboarding or contract changes.
• RETIRED: Machine is hidden from the system and no longer managed or monitored.

• LOCAL: Partially monitored machines (e.g., USB-connected) where data is estimated.
• NET: Network-connected machines.
• NETLESS: Not connected to a DCA or SNMP tools. Data (meters, errors) must be entered manually via the Cloud.

Machines marked as NET or LOCAL but not actually monitored should be reclassified as NETLESS to ensure proper manual management.

Machines can be created in three ways:

Automatically via DCA Discovery: When a DCA scans the network, it can automatically detect devices, match them to the appropriate contract, populate machine records with key details like model, variant, and serial number, and begin monitoring immediately.

Manually via Excel Import or UI Entry: Users can add machines manually by importing data via Excel or by entering machine details directly through the UI under MPS > Contracts > Equipment on Contract.

Automatically Upon Equipment Delivery: When equipment is delivered through Noetics, the system automatically creates a machine record under the contract. It is initially marked as NOT INSTALLED, with placeholders for model and other fields. Once the DCA detects the device and identifies it, the system updates the machine’s status to INSTALLED, sets the actual model, and enables monitoring if applicable. 

To add a machine manually:

1. Go to MPS > Contracts > Equipment on Contract
2. Click New to create a machine record
3. Enter the required details (model, serial number, etc.)
4. Set the Class to NETLESS if the device is not monitored by a DCA

Marking a machine as NETLESS tells the system to expect manual meter entry rather than automated SNMP readings. This is important to ensure correct billing behavior and service tracking.

If you're manually adding a machine and don’t see the correct model:

• If the machine is monitored by a DCA, set the Model to "Discover" and the Status to Not Installed. The DCA will detect and assign the correct model automatically once it scans the device.
• If the machine is NETLESS (not monitored by a DCA), choose the closest matching model available — for example, select “Bizhub 328” if your device is “Bizhub 328e".

If no close match exists, contact us and we’ll add the model for you.

In Noetics, your Machines in Field are tracked under MPS > Contracts > Equipment on Contract. This section displays all devices linked to contracts, whether they are under review or fully managed.

Machines in a PILOT contract are considered unmanaged — their meters are collected, but they are not included in billing, service, or consumable workflows. Once reviewed and moved into an ENTERPRISE contract, they become part of your Managed Install Base. This clear separation ensures your team has visibility into all devices in the field while maintaining control over which machines are actively billed and supported.

To retire a machine, go to MPS > Contracts > Machines on Contract, search for the machine’s serial number, and update its status to RETIRED. You should also set the Retired Date to reflect when the machine was officially retired.

A machine is considered offline when it stops communicating with the system through its assigned DCA. This usually means the device is no longer reporting data—like meter reads or consumable levels—due to being powered off, disconnected from the network, or blocked by configuration issues. Offline machines are not being actively monitored and may miss key alerts, supply orders, or billing updates. In Noetics you can adjust for how many days the machine should not report before it is marked as offline.

Our system can automate communication with the key operator on each machine via email and/or SMS to ensure the machine gets back on the DCA.

In Noetics, offline machines are automatically detected by checking the last reading timestamp from the DCA. Devices that haven’t reported within the defined offline threshold (measured in hours) are considered offline and are highlighted in red in the system. You can view these machines by navigating to MPS > Devices > Device Status and selecting the “Offline” filter. The exact time of the last update is shown per machine, and no manual action is required—when the machine comes back online, the system updates its status automatically.

Yes. Go to MPS > Devices > Device Status, open the serial, and in the Management tab set the Offline Threshold (Hours) value to the desired time frame.

The Noetics Panel is a web-based dashboard to manage printers in real time. It allows users to view active devices, enter manual counters, manage alerts, configure email notifications, and group consumable shipments. The Panel is also used to customize screen views, define shipment schedules, and monitor devices based on criteria like activity, threshold status, and assigned projects. It works alongside Cloud tools to support billing, visibility, and service workflows. Once a machine becomes part of a contract it will get its own micro site that allows both the customer and the dealer to see and manage details of that machine.

Yes. Both interfaces are fully synchronized. Mass updates are typically done in PANEL, while detailed, machine-specific adjustments are handled in ERP. Any change made in one is immediately reflected in the other.

The preferred approach is a DCA-first process. This means importing customers and contracts (including both Pilot and Enterprise types), then assigning a DCA to the Pilot contract. The DCA will scan the network and automatically create machine records. Afterward, static data (like install date and billing rates) is enriched through Excel import. This method is faster, more accurate, and provides a better audit trail than manually loading all machine data upfront.

While this data exists in the DCA, syncing it automatically via API would overwrite any user updates made in Noetics or through the customer-facing PANEL. To avoid unintentionally erasing local edits, it's recommended to import location or operator data once during onboarding and maintain it manually afterward.

Machines that are not found in the DCA but were imported should be reviewed. If they belong to terminated contracts, they should be marked as RETIRED. If they are no longer monitored, consider updating their class to NETLESS so they can be manually managed through the Cloud interface.

When a machine is loaded with Model = Discover and Status = NOT INSTALLED, the system waits for a DCA read. Upon first read, the correct model is assigned. Once assigned, the machine can be switched to INSTALLED and invoicing/alerts will begin.

“Toner Only” machines are those for which only toner is included in the service contract—other consumables like drums or fusers are excluded.

To configure:

• Turn OFF thresholds for excluded consumables (e.g., drum, fuser) in the machine record.
• Use % thresholds (not days remaining) to trigger toner-only alerts and orders.
• “All Inclusive” machines will have all relevant thresholds active for full monitoring and supply fulfillment.

The "Machines Managed" count on a contract shows all machines linked to that contract, regardless of their current status (e.g., Installed, Not Installed, Retired). This count is not automatically filtered based on activity status.

If you want to see only active or billing-eligible devices, you can use the saved filters at the top of the view — such as:

• "Active" – shows machines that are Installed
• "Pending" – shows machines that are Not Installed

To ensure that inactive machines (like those marked as Retired) don’t clutter your view or get miscounted in billing prep:

• Mark the machine’s status as Retired under MPS> Contracts > Machines on Contract — this removes it from billing eligibility.
• When viewing "Machines Managed" from a contract, use the "Active" filter to see only Installed machines or the "Pending" filter to view Not Installed machines.
• To get a full picture of all non-retired machines, you can combine both filters or create a custom one that includes both Installed and Not Installed statuses, while excluding Retired.

In Noetics, consumables are tightly integrated with machine monitoring and supply automation. For any machine monitored by a DCA, Noetics automatically identifies the OEM consumables for that model. You simply choose which ones to keep and set pricing — no manual entry required.

If you want to manually make a consumable in the system, you can go to Inventory > Products > Products and start making a new part where the key fields are:

• Product Name
• SKU/Part Number
• Consumable checkbox enabled
  
• Product Category set to Consumables
  
• Template Tags listing the compatible machine models
  

Key features of consumable management in Noetics include threshold-based automation, manual override options, and intelligent handling of low-resolution data. Each consumable has a configurable threshold, commonly set to levels like 20%, that determines when action should be taken. When a monitored machine's consumable falls below the defined threshold, Noetics can automatically generate a consumable order, create an inventory transfer and shipping confirmation and even a purchase order if you don't have that part in stock. In addition to automated workflows, the system also supports manual overrides, allowing users or customers to place consumable orders directly when needed. 

Consumable orders in Noetics are requests for toner, drums, or other supplies. These can be generated automatically when a monitored machine drops below its configured threshold, triggering a Consumable Alert. This alert can be converted into a Sales Order, which then drives inventory transfers or purchase orders if stock is unavailable. Orders are only generated for machines marked as INSTALLED and assigned to ENTERPRISE contracts.

Manual orders are also supported — either directly in the system or by customers via the printer’s microsite (for NETLESS machines). Vendor sourcing is controlled per machine under the Shipment tab, ensuring flexibility in fulfillment. Machines in PILOT or NOT INSTALLED status are excluded from automation.

Consumable catalogs in Noetics are organized lists of part numbers (SKUs) used to match supply alerts with the correct reference. Catalogs are grouped by origin, such as OEM, remanufacturer, or third-party vendor, and ensure that each device or customer receives the appropriate consumable, even if they don’t use OEM parts. These consumable catalogs are key to define and connect to machines to leverage the full automation of the system.

There are three catalog types:

• OEM: Preloaded, system-provided references. These cannot be modified. Will be added for you for every new model read by the DCA
• OEM-Zone: Vendor that provides you OEM consumables that are not the actual OEM
• Vendor: Alternative references. This is the highest-priority source for matching alerts.

Each dealer in Noetics can maintain their own consumable catalog, defining the specific toner, drum, or supply SKUs available for their machines. These catalogs ensure the correct items are used for both automated and manual consumable orders, whether OEM, remanufactured, or vendor-specific.

To create a new catalog, go to MPS > Settings > Consumable Vendors, then:

• Add a Name and Description
• Choose a Type: OEM (default and non-editable), Master, or Vendor
  Catalog types follow a priority hierarchy used during supply alert resolution.

Catalogs are typically created from validated data files and must be thoroughly reviewed to catch errors like missing codes or duplicates. If issues are found, the catalog undergoes a second validation round before it can be activated. Once finalized, it's linked to the environment and used to determine which SKUs are triggered by supply alerts and available for ordering.

Noetics follows a strict catalog hierarchy:

• First, it checks the Vendor catalog.
• If not found, it checks the Master catalog.
• If still not found, it defaults to the OEM catalog.

This ensures that the system always uses the correct SKU—even for third-party or mixed-brand environments.

Custom catalogs let you:

• Use third-party or remanufactured consumables.
• Assign different part numbers to the same model depending on the client.
• Ensure alerts and supply orders are accurate—even with non-OEM consumables.
  This reduces inventory errors, avoids confusion, and supports clients with cost-saving preferences.

Go to: MPS > Settings > Consumables

• For small quantities, manual entry is recommended.
• For large batches, use CSV or Excel import.

Each reference should include:

• Part Number
• Model
• Consumable Type
• Alias (optional)
• Vendor (must already exist)
• Description
• Durability
• Optional pricing fields

Do not upload SKUs already present in another catalog.

Yes. Go to Contacts, find the customer, and under the Preferred Consumable Catalog  tab select “OEM” (or any preferred vendor) for all machines that that customer will have.

Yes. Go to: MPS > Contracts > Machines on Contract > Select a machine > Shipment tab, and select the catalog under the “Vendor” field for that device.

This overrides the customer-level catalog only for that machine.

Yes. Go to Settings > Sales > Consumable Catalog to define a system-wide default catalog used when no customer- or device-specific assignment is made.

If a reference isn’t found in the assigned catalog, Noetics will automatically check the next catalog in the hierarchy (Vendor → Master → OEM) until a valid match is found. This guarantees that the alert will always point to a usable SKU.

Yes. For every product in your inventory, you can define minimum and maximum thresholds. These settings allow the system to either recommend or fully automate order creation when stock levels go below the defined minimum.

You can configure this in Inventory > Configuration > Reordering Rules.

• Use the Counters App in the PANEL to view registered meters.
• The Cloud view for each printer also shows a histogram of monthly page volumes.
• For broader reporting (fleet, project, or client level), use the Charts App.

Noetics stores all meter readings for 12 months. After that, only the last meter record of each month is retained to preserve usage history while optimizing storage.

Yes. Customers can access the printer’s microsite and use the "Enter Counters" button to submit readings. This only works for NETLESS machines.

Yes. Go to MPS > Contracts > Machines on Contract, select the serial number, and click Open Cloud. From there, click Enter Counters and submit the meter reading. For color devices, enter both Total Counter and Color Counter — the system will calculate black automatically.

Yes, importing historical meter readings by serial number is possible. You can prepare a list with the last invoiced meters and dates and upload it to update existing contracts.

The "Enter Counters" option is only available for machines marked as NETLESS. If a machine was previously labeled as NET and recently changed to NETLESS, it may take time for the change to be fully registered by the system. If the feature doesn’t activate, ensure the classification has been saved and is recognized by the PANEL.

Yes. When setting up a custom counter, you can assign it to all partners or restrict it to a specific sales channel by selecting the Partner field.

Once saved, the new counter is immediately available across all monitored printers of that model. There's no need to update the DCA or visit customers.

A contract invoice in Noetics is a billing document generated based on meter readings and pricing rules defined on machines under Enterprise contracts. These invoices are typically created monthly in DRAFT state, giving your accounting team time to review, adjust, and send them individually or in bulk.

Contract invoices reflect charges calculated from current meter data, contract terms, and any applicable proration for machines added mid-cycle. Devices under Pilot contracts are excluded from invoicing. Invoices are visible in the built-in customer portal, and customers can pay directly via credit card or ACH using Noetics’ integrated fintech solution.

To enable automated invoicing for a customer:

1. Go to Contacts > Customers
2. Open the customer record
3. Navigate to the Sales & Purchase tab
4. Enable Auto Invoice
5. Set the Invoice Cycle (day of the month to generate invoices)

Once enabled, Noetics will automatically generate a draft invoice each month on the specified billing day. The system collects meter readings from all ENTERPRISE contracts linked to the customer and calculates charges based on pricing rules and usage. The invoicing engine also supports proration.

You can manually invoice customers using the Manual Invoice wizard. Here’s how:

1. Go to MPS > Roles > Customers
2. Select one or more customers
3. Click Actions > Manual Invoice
4. In the popup, choose one of the following options:

• Only meters – Pulls meter data and stores it in Operations > Counters. It’s useful for reporting or preparing to invoice. Be sure to set the "To Date" to today and click Invoice.
• Only invoice – Uses existing meter data to apply billing logic and generate charges
• All – Pulls current meters and runs invoicing in one step (recommended)

Only machines on ENTERPRISE contracts will be included in billing. Machines in PILOT can be read for meters but are excluded from invoicing.

To configure how a specific machine is billed, follow these steps:

1. Navigate to MPS > Contracts > Machines on Contract and Select the machine you want to configure.
2. Installation Status: On the Installation tab, ensure the machine’s Status is set to INSTALLED.
3. Go to the Invoicing Tab and configure the following:

➤ Minimum Type Mode:

• NONE – No allowances; bill actual usage only.
• SEPARATED – Use separate covered copy counts for Black & White and Color meters.

➤ Invoicing Group:

• STANDALONE – The machine is billed independently with its own base and overage rates.
• GROUP1 to GROUP10 – Use these if machines share covered copies across a group.
  • Example: Use GROUP1 if all machines share the same pool of covered B/W and Color copies.

➤ Covered Copies and Rates:

• Minimum (Black or Color) – The number of covered copies (included in base).
• Price Over Minimum – The rate per page beyond the covered copies.
• Price Under Minimum – Usually 0, unless billing underage differently.

➤ Monthly Flat Fees (Optional):

You can assign up to four fixed-cost charges on the right side of the invoicing tab:

• Maintenance – Typically the contract’s base charge (if not using meter group bases).
• Leasing – Used when you bill the lease to the customer and pay the leasing company.
• Other 1 and Other 2 – For any additional recurring charges (e.g., accessories or service plans).

Noetics supports several fixed-cost fields on each machine, including Maintenance, Monitoring, Leasing, and two customizable fields: Other 1 and Other 2. The maintenance is automatically calculated based on the setup during quoting as allowance * base rate with the option to adjust the price up or down, with the proper permissions.

• Maintenance, Monitoring, and Leasing charges are automatically prorated if a machine is installed mid-cycle. The system uses the later of the Install Date or Contract Start Date to calculate the prorated amount.
• Other 1 and Other 2 are used for miscellaneous monthly charges that should always bill the full amount — they are not prorated.

The labels for Other 1 and Other 2 can be customized to match your preferred billing language, making them useful for flexible, recurring fees.

The billing start date for each printer is set based on the Install Date found under: MPS > Contracts > Machines on Contract > [Machine] > Installation tab

To begin billing, the machine must be in INSTALLED status. The system will use the Install Date or the Contract Start Date, whichever is later, as the starting point for billing. From there, the billing cycle is calculated based on the last invoice date and the "To Date" entered during invoicing. For example:

• If no invoice has been generated yet, billing starts from the install date.
• If the last invoice was on 01/01/2025, and the next invoice uses 01/15/2025 as the To Date, the system will bill for the period 01/02 to 01/15 — a 14-day cycle.

The system always begins billing the day after the last invoice, up to and including the selected To Date.

If an invoice was created using incorrect pricing (e.g., a wrong per-page rate was entered in the Invoicing tab):

1. Delete the invoice in Noetics MPS > Contract > Contract Usage
2. Correct the rates on the machine or contract record.
3. Return to the customer record and use the Manual Invoice action to regenerate the invoice.

There’s no need to change the meter values or the last invoiced date. The system will use the existing meter data for the new invoice.

If the mistake was in the meter values used during invoicing:

1. First, delete the invoice — this is required to unlock the meter records.
2. Go to Operations > Counters and delete the incorrect meter entries.
3. Once removed, the system will automatically update the last invoiced date and allow you to re-enter the correct values.
4. Return to the customer and regenerate the invoice using the Manual Invoice action.

• You must delete the invoice first before deleting any associated meters.
• You can only delete the most recent meter readings. Older readings cannot be removed if newer ones exist, to preserve the meter evolution logic.

Yes. You can combine equipment lease charges and MPS service fees into a single invoice. This is done by populating values in the "Monthly Flat Fees" fields on machine records. The system picks up those values and includes them in the generated invoice, aligning with the one-invoice model.

Yes, in Noetics you can maintain your in-house leasing company for the full lease lifecycle including Fixed Asset management and depreciation. If you share the CoA or have a totally separate one, we can maintain both in one database and control access, reporting and functions independently.

Noetics currently integrates with the following leasing companies:

• Great America
• US Bank
• Wells Fargo

More integrations are planned as the platform evolves. Being on a open source platform, we're only limited by the technology of the company we integrate with.

Yes, in Lease Management > Rate Cards, you have the ability to create and edit rate cards, manually or through an excel export and import.

Lease costs can be handled in two ways:

• Option A: Assign the full lease cost to a single “master” machine in the group.
• Option B: Prorate the lease amount across all machines in the contract. This method is ideal for contracts where the install base may change over time.

The lease cost is then added to the invoice using the Leasing field and prorated automatically based on billing cycle duration.

A coterminous lease aligns the new lease with the remaining term of the original lease. In practice, this means:

• The leasing company offers a reduced term (e.g., 50 months instead of 60) for the new device.
• The equipment is added to the master lease via a Schedule A document.
• The system should reflect this by either:
  • Adding the full lease value to a “master” printer, or
  • Prorating lease costs across machines using designated fields (e.g., Lease Payment).

You can use the Lease Payment field to capture individual lease charges per machine. For example:

• Enter the full lease value on the master machine, and set all others to 0.
• Or spread the lease values across machines. The system will total these and include them in the invoice.

This setup supports multiple leases under a single invoice, with no extra configuration required from the customer side.

If each location is treated as a separate customer (which is often the case in ERP systems), then the recommended approach is to create a separate contract and customer record per location. Machines discovered by the DCA can be assigned to the appropriate contract, and the customer address will auto-populate at the printer level. This also ensures that each location gets its own invoice.

Alternatively, if all locations fall under a single customer, users can manually update the Company and Location fields on each machine. This allows the same customer record to reflect different physical locations.

If a machine was skipped due to missing meters or other issues, don’t worry. If you enter the meters after billing, the system will automatically include the usage in the next billing cycle. Alternatively, you can manually trigger an invoice to catch up the missed charges.

Invoices will not generate if the contract is of type PILOT. PILOT contracts are non-billable by design—they allow monitoring and setup but do not support invoice generation. To enable invoicing, machines must be moved to an ENTERPRISE contract.

The system calculates Black pages as Total minus Color. If the Color count exceeds the Total, it results in a negative value, which is invalid. In such cases, the system blocks invoicing to avoid incorrect billing. Ensure that the Color counter is equal to or less than the Total counter.

Yes, you can manually enter counters via Open Cloud and attempt to trigger invoicing using the “Only Invoice” button. However, this only works if the machine is under a billable (ENTERPRISE) contract. Also, this workflow does not function in test databases unless specific configurations are enabled—otherwise, it may affect production-linked data.

Noetics supports billing meters from multiple machines under a shared group allowance. To do this, assign all relevant machines to the same Invoicing Group (e.g., “Group1”) and ensure their Minimum Type Mode is set to allow combined billing.

There are two ways to split the allowance within the group:

• Equal Split: Assign equal minimums to each machine (e.g., 3,750 each for a total of 7,500).
• Single-Device Assignment: Assign the full allowance to one machine (e.g., 7,500 on one, 0 on others). Note that if new machines are added later, the total must be updated manually to reflect the correct allowance.

This setup allows usage across all grouped machines to be calculated collectively for billing purposes.

Yes. You can group machines for black meters only, while leaving color meters billed separately. For example, in a 3-machine setup, you could set a shared black allowance for Group1 and assign 0 allowance for color, which would then be billed independently per machine.

No. In the current system, each machine can only belong to one billing group, and that group defines the pricing logic for both black and color meters. Unlike some other platforms, dual group assignment is not supported.

Minimum types define how allowances are set for each machine on a contract. You have three options:

1. Separated

• Define separate allowances for Black & White and Color copies
• Ideal when you want to bill or track each type independently

2. None

• No minimum allowance is set for the machine
• All usage is billed as overage

There are two types of billing approaches when it comes to leasing:

• Bundled - The dealer will bill for the lease payment on their monthly contract invoice and then on a agreed-upon cadence remit the collected funds to the leasing company
• Traditional - The customer will receive an invoice from the leasing company for the lease payment and the dealer will bill for their service as per the contract
• Traditional can come with 
• • Pass Through Service - the dealer will invoice the leasing company for the usage and let the leasing company collect the payment for the lease and the service and send the service portion to the dealer.
  • Pass Through Maintenance - we charge the maintenance to the leasing company instead of the customer, but charge the overages (usage) to the customer. The leasing company collects the lease payment and the maintenance.

The billing approach is determined by the configuration on the Sales Order. Noetics will automatically:

• Calculate the lease payment per machine
• Include lease charges on the contract invoice
• Create a linked lease record tied to both the contract and sales order
  

This ensures all billing flows are consistent, automated, and properly tracked—whether the customer pays the dealer, the leasing company, or both.

Yes. Annual contract escalation is supported and allows to automatically increase CPI (cost per impression) rates, overage charges, and maintenance fees each year based on the contract’s start date. Escalations can be configured either system-wide (for all contracts) or per contract, with separate percentages for each charge type and for each year—up to seven years.

The system uses a daily automation process to check active contracts and apply the correct increases each year. Proration, contract types, and machine-level billing settings are respected, ensuring that escalations apply only where intended. This helps keep pricing aligned with inflation, rising costs, or long-term agreement terms, all without manual updates.

Yes. You can mark each contract to indicate if it uses meter group bases or not.

Yes, no matter if you use meter group bases or not you will be able to add distribution codes to machines which will ensure the system splits the supply / service pieces and based on that you can define GL accounts that need to be hit ensuring a smooth and accurate invoicing flow every time.

Depending on your choice it can be through one of our integrated partners Avalara or TaxCloud, or manually. Noetics has the capabilities of managing tax tables and rules and even have automated application of right taxes to documents using our Fiscal Positions. Our system comes with build in Tax Reporting tools standard for GAAP accounting.

Noetics supports two types of consumable thresholds:

• Percentage-based (e.g., 20%)
• Day-based (e.g., 7 days remaining)

You can manage and update these thresholds either in the ERP or the PANEL:

In the ERP:

1. Go to MPS > Device Reporting > Device Status
2. Find the machine by serial number and open its detail view
3. Adjust thresholds for each consumable under the Consumables tab

In the PANEL (Status App):

• To modify percentage thresholds: Click the Thresholds icon next to the printer and adjust the values
• To switch to day-based thresholds:
  • Use “Activate threshold in days” to apply the setting to all printers in a project
  • Or manually adjust it per printer by clicking the Thresholds icon

Thresholds can be customized per consumable and per machine. The default is 20% for percentage-based alerts. When a threshold is reached, Noetics automatically generates a supply alert.

Because percentage levels are not meaningful on their own. For example, 20% toner remaining may last 3 days on one printer and 3 weeks on another. Without context like device usage patterns, percentage-based alerts can lead to inefficient or mistimed consumable orders.

Day Management is a system that replaces percentage-based thresholds with remaining days. Instead of defining a low-percentage alert, you define how many days in advance you want to be warned before a consumable runs out. This ensures more accurate and proactive replenishment.

You can activate it through:

• PANEL: Go to Status App, click the indicator in the “Thresholds” column, and switch from percentage to days.
• ERP: Go to MPS > Device Reporting > Device Status > Open a device > Consumables tab, and change the threshold type from percentage to days.

Noetics uses an AI engine to analyze each printer’s historical usage and real-time consumption rates, converting percentage levels into estimated remaining days. These predictions improve over time as the system observes more usage patterns.

If a printer doesn’t have enough historical data—such as newly added devices or those with irregular use—Noetics will automatically fall back to traditional percentage-based thresholds to maintain reliable alerting.

Yes. Noetics allows hybrid management. You can configure each machine individually to use either percentage or day-based thresholds, and switch between them at any time.

A threshold is considered “at risk” when the number of days remaining is less than the alert margin. For example, if you set a 30-day threshold but the printer consumes a cartridge every 7 days, the system will flag that it's unlikely to meet the 30-day target with a single supply.

In PANEL, at-risk printers appear greyed out, and a banner is shown in ERP.

Technically, Day Management can be activated from day one, but it is recommended to wait at least one month to allow the system to collect enough historical data for accurate predictions.

Alerts are proactive notifications that inform you when a consumable in a printer is approaching its threshold and needs to be replenished. Noetics monitors each consumable individually, regardless of whether the printer can report levels, and triggers alerts based on granular level data or estimated remaining days.

Once a consumable reaches the alert threshold, Noetics generates a single notification and waits until the cartridge is installed. Only after installation is confirmed does the system close the alert. This prevents repeat notifications and avoids accidental duplicate shipments.

If certain consumables aren’t monitored, downtime risks remain. To ensure full automation and efficiency, every consumable in every monitored printer should be tracked. If any consumables are missing from a model, you can request their addition via your Noetics representative.

A technical alert is a system-detected fault reported by a DCA-monitored printer, such as a damaged drum or other hardware issue. When registered by a DCA, Noetics automatically generates a service ticket in the Helpdesk/Dispatch module, where it can be reviewed and dispatched according to your workflow rules.

The system will detect technical alerts and generate a service ticket automatically.

Customers can also request service manually through:

• The printer's mini website
• A form hosted on your website
• An email to a monitored inbox
• Or you can enter the request manually

You can manage work orders, dispatch technicians, track time and materials, and capture customer signatures—all from a single view.

Tasks can be created manually or triggered from a sales order or helpdesk ticket. Each task includes location, scheduled time, assigned technician, and required products or tools.

Yes. When a service ticket is created, the system shows the serial number and the contract (if the machine is under one) directly on the service order. This helps techs quickly confirm whether the machine is covered. We also leverage our tags to ensure the tech sees how a machine is tagged to understand, for example, what SLA policies apply to the machine

Yes. Field staff can log in from mobile or tablet. They see assigned tasks, directions, customer info, and can record time, materials, and notes on-site.

Technicians can record parts or materials consumed directly on the task. Inventory is updated automatically based on the assigned stock location.

When a technician pulls a part that’s not in their inventory, the system checks all other available locations (including other technician trunks). If it finds the part in another uncommitted location, it will generate the proper transfer and inventory documentation. If no stock is available, the system automatically creates a purchase order and related documents to procure the part.

Yes. Technicians can log time manually or use timers. Each entry is tied to the task and can be included in reports or invoices.

You can collect a digital signature directly on the technician’s device. The signed report is saved to the task and included in the final invoice or service summary.

Yes. Tasks can be linked to billable products, time, or fixed fees. Once completed, an invoice is generated from the recorded work and sent to the customer.

Dispatchers can view all tasks in a calendar or Gantt view. Tasks can be assigned, reordered, or rescheduled with drag-and-drop. Technicians get real-time updates.

Dashboards show KPIs like average time per task, on-time completion, parts usage, and customer feedback. You can filter by technician, region, or service type.

Yes. A helpdesk ticket or CRM lead can trigger a service task. All related records stay linked, so sales, support, and service stay aligned.

Each ticket can reference warranty status, SLA terms, and contract coverage. You can restrict billing or set deadlines based on service agreements.

The Replenishment screen shows which products need reordering based on stock levels, demand, and lead times. It also explains why each item is needed (e.g., low stock, forecasted usage, or open orders).

For deeper planning, the Forecast Report shows real-time inventory levels—including on-hand, committed, and incoming quantities. This gives a full view of inventory movement and helps plan purchases with confidence.

From the Replenishment screen, you can generate purchase orders with one click. Noetics calculates quantities, selects the correct vendor, and drafts the PO automatically. You only need to review and confirm.

Yes. You can set minimum and maximum stock levels per product. When stock drops below the minimum, Noetics automatically prepares a draft purchase order using the assigned vendor and lead times.

Noetics provides dashboards that track delivery lead times, fulfillment accuracy, and vendor responsiveness. You can review this data by vendor or product to improve sourcing decisions.

Live reports in Noetics let you break down spending by vendor, product, or category. You can filter by time period, compare trends, and export data for financial tracking or budgeting.

Confirmed purchase orders become shared records across departments. Accounts Payable can generate bills, Inventory sees incoming products, and the data flows into financial reports. No re-entry is needed.

Vendor pricelists are maintained in Noetics. When a product is added to a PO, the system applies the correct price based on vendor settings, quantity brackets, and contract terms.

Yes. Each PO line includes a one-click view of purchase history. You can instantly see the last vendor, price, and delivery lead time, helping your team act quickly and accurately.

Noetics supports approval workflows based on value or department. You can route purchase orders for review before they’re confirmed, without interrupting daily ordering processes.

You can attach any file—contracts, product sheets, certifications—directly to the PO. This keeps all related documents accessible in one place for purchasing, warehouse, and AP.

Everything runs in one shared system. POs update inventory and accounting automatically. Pricing, receipts, invoicing, and approvals stay in sync without manual follow-up.

Vendor bills can be created from purchase orders, received by email, or entered manually. You can track due dates, record payments, manage approval flows, and reconcile bills against bank transactions.

Invoices can be created from sales orders, subscriptions, or manually. Noetics tracks due dates, payment status, and sends reminders. Customers can pay online through the portal.

Yes. Bills can be auto-created from confirmed purchase orders or extracted from incoming emails. You can assign an email like bills@yourcompany.com to your AP inbox—when vendors send PDFs, Noetics reads the file and creates a draft bill. Invoices can also be auto-generated when sales orders are confirmed or delivered, streamlining both AP and AR workflows.

Noetics uses OCR and AI to extract data from incoming PDF bills, automatically identifying fields such as vendor, invoice number, invoice date, due date, currency, taxes, total amount, and structured line items. It also attempts to match the bill to an existing purchase order. Over time, the system learns from manual corrections to improve accuracy and reduce entry errors.

Yes. If the invoice references a PO or matches the vendor and total, Noetics suggests a matching PO. You confirm or reject the match before posting.

Every bill created from email or OCR stays in draft until someone reviews it. You can adjust amounts, change accounts, or reject the entry entirely.

Credit notes can be created from any invoice or bill. These can be applied to open amounts or processed as refunds, with full reconciliation supported.

Yes. Aging reports group open items by date range. You can view totals, sort by partner, and drill into each document. Reminders or payment follow-ups can be sent directly from the system.

Yes. You can register a single payment and apply it to several documents. Noetics handles partial payments and shows remaining balances.

Invoices can be paid with CC or ACH. Customers access the payment link directly from the portal or email.

Import bank statements or sync with your bank. Noetics matches payments and receipts to open items automatically. You confirm matches or reconcile unmatched lines manually.

Yes. You can define approval workflows. Bills can require validation from a department manager or finance lead based on rules like total amount or vendor type.

Bank sync connects your live bank accounts to Noetics. Transactions import daily or on demand. This allows real-time reconciliation of payments and receipts with open invoices and bills—reducing manual entry and avoiding mistakes.

You can reconcile directly from the bank feed:

• Match payments with invoices or bills
• Create missing payments
• Handle partial payments or overpayments

Bank sync shortens the monthly close cycle, improves cash flow visibility, and gives finance teams full control over incoming and outgoing transactions.

Yes. Noetics matches payments to multiple invoices or bills and supports batch reconciliation. You can also reconcile manually when automatic matching doesn’t apply.

Yes. Before confirming a bill or invoice, you can preview the exact journal entry—debit and credit lines, accounts used, tax impact, and analytic tags. This ensures accuracy before affecting your books.

You can cancel the entry, correct the issue, and repost it. If the document is locked (e.g. due to payment or posted period), you’ll need to issue a credit note and create a corrected version. All corrections are fully traceable in the audit trail.

All documents—including original PDFs—are stored on the bill. Every action is logged in the chatter, so you have a full history for audit and compliance.

All bills and invoices feed into real-time financial dashboards. You can forecast cash flow, monitor overdue items, and track AP/AR balances by partner, category, or time period.

Noetics includes standard and advanced reporting for both areas:

AP (Vendor):

• Aged Payables (by vendor, due period)
• Vendor Ledger (detailed transaction history)
• Payment Status
• Cash Forecast (based on due bills)
• Payables per Analytic Account or Department

AR (Customer):

• Aged Receivables (by customer, due period)
• Customer Ledger (full invoice/payment view)
• DSO (Days Sales Outstanding)
• Revenue per Customer/Product
• Payment Follow-up Analysis

All reports are filterable by date range, partner, currency, salesperson, or analytic tag. You can export to Excel or schedule them to be sent automatically to your team.

Noetics uses full double-entry and accrual-based accounting. Every financial transaction affects at least two accounts. Revenue is recognized when earned, and expenses when incurred, not when cash moves.

You can define fiscal years and monthly periods. Before closing a period, you can run checks for unposted or unbalanced entries. Once closed, no edits are allowed—ensuring a clear audit trail.

Yes. You can defer revenue or expenses using recurring journal entries or automated recognition schedules. This helps align revenue and costs across periods per GAAP requirements.

You can define depreciation schedules (straight-line, declining, manual), asset categories, and posting frequency. Noetics generates journal entries automatically across periods.

Inventory is valued using FIFO or Average Cost. Real-time inventory valuation posts entries as products move, tying cost of goods sold to deliveries.

Use a dedicated journal or analytic tag for year-end or audit adjustments (e.g. depreciation corrections, bad debt reserves). This keeps operational and adjustment activity separate.

Yes. You can define approval workflows for journals. This ensures that adjusting entries or financial corrections go through proper validation before being posted.

Noetics includes:

• Profit & Loss
• Balance Sheet
• Trial Balance
• General Ledger
• Cash Flow (indirect method)

All reports can be filtered by period, analytic tags, journal, or business unit.

Yes. All accounting records track full history—who created it, posted it, edited it, and when. PDF copies, notes, and comments stay attached permanently.

Employees can enter expenses directly in the Expenses app. Each entry includes the amount, description, date, and receipt. Expenses can be submitted individually or grouped into a report.

Multiple expenses can be added to one report. Once submitted, the report follows your company’s validation rules, such as department or finance-level approval.

You can define approval routes based on employee role, department, or amount thresholds. Noetics automatically sends the report to the right reviewer.

Receipts are attached directly to each expense line. Employees can upload files, drag and drop images, or snap a photo with the Noetics mobile app for instant capture.

Managers see pending reports in their dashboard. Each line shows the amount, description, and attached receipt. They can approve, reject, or request changes with a comment.

Each expense is marked as either “Paid by Employee” or “Paid by Company.” This affects reimbursement and accounting entries. Reimbursable expenses generate a payable entry to the employee. You can handle this through the same payment process used for vendors. Noetics tracks the payment status automatically.

Yes. You can tag each expense with an analytic account, project, or department. This allows you to report on spending by category, initiative, or client.

Once approved, Noetics posts each report to the general ledger using rules from your chart of accounts. The correct accounts are selected based on the expense product. If you use Noetics Payroll, reimbursements can also sync directly into payslips. All transactions are traceable and follow your chart of accounts.

Yes. You can predefine expense items like mileage, meals, or hotel. Mileage can be calculated with a fixed rate per km or mile, applied automatically based on distance.

Set category limits, block unapproved items, and use approval routing to enforce policy. Managers can see a history of spending and compare it to internal rules.

The Documents app lets you store, organize, share, and track files within a structured workspace. You can set up folders by department, tag documents, and control access by user role.

Files can be uploaded manually, emailed into a folder, or generated automatically from other apps like Invoicing, HR, or Projects. Each document stays linked to its source record.

In Noetics, you can create structured folders by department or purpose—such as “Contracts,” “Invoices,” “HR Files,” or “Legal.” Each folder can have tags, default permissions, and automated actions. Access to both folders and individual documents is controlled by security groups, ensuring only authorized users can view, edit, or approve files based on their role.

Documents in Noetics are fully integrated across the system and can be attached directly to any record—such as a vendor, employee, sale order, or task—providing full context without switching between apps. This tight integration allows documents to support workflows across Sales, HR, Projects, Inventory, and Accounting. For example, a contract created in Sales can trigger an approval flow, link to a purchase order, and automatically sync with financial records.

You can search by name, tag, content, date, or related record. The search bar works across all folders and attached documents, not just file name.

Yes. You can generate a secure public link to share with external partners. You can also set expiration dates or limit access to view-only.

Documents can be routed through approval steps. You define reviewers, assign deadlines, and track validation status for contracts, policies, or sensitive uploads.

Yes. Rules can be set up to auto-assign documents to users, move files based on tags or status, or request approvals after upload.

Yes. Standard forms like NDAs, onboarding checklists, or quote formats can be stored and reused as templates, ensuring consistency across teams.

Each document keeps an activity log. You can see who uploaded, approved, shared, or edited a file—and revert to older versions if needed.

You can send documents for signature directly from the system. Recipients receive a secure link, sign electronically, and the signed document is saved back to the record it came from.

Any PDF—quotes, contracts, NDAs, onboarding forms, or internal approvals. Documents can be uploaded manually or generated from Sales, HR, or custom apps.

Once signed, the document is locked, time-stamped, and saved to the original record (e.g. sales order, employee file). No separate upload is needed.

Yes. You can specify who signs, in what order, and where on the document. For example, a manager signs first, followed by a customer or employee.

Yes. External users receive a link by email. No login is required. They can review and sign on any device—desktop or mobile.

Each request shows real-time status: pending, signed, or refused. You can also send reminders or cancel requests from the dashboard.

Users can customize forms, views, reports, and workflows using Studio. You can add fields, change layouts, rename labels, and set visibility rules—no developer needed.

Yes. You can add text, selection, boolean, monetary, relational fields, and more. You can also define default values, conditional visibility, and required field logic directly in the UI.

Approval steps can be added to any document type—like POs, expenses, or sales orders. You define who approves, in what order, and under which conditions (like amount thresholds or departments).

Automated actions in Noetics let you trigger updates, field changes, record creation, or notifications based on specific conditions—without writing code. These automations can also work across apps. For example, marking an opportunity as “Won” can auto-assign tasks, closing a support ticket can trigger a satisfaction survey, or completing a sale can create a follow-up task in another module.

Yes. Use automated actions or marketing automation flows to send emails or SMS messages based on triggers—like order confirmation, deadline missed, or stage change.

Yes. You can create pivot tables, graphs, cohort charts, and custom dashboards with filters. These views update live and can be shared across teams.

For more advanced logic, server actions and scheduled jobs can be defined. These run in the background, updating records or triggering flows based on time or conditions.

Yes. Noetics offers built-in API endpoints, webhooks, and scheduled jobs to sync data with ERPs, CRMs, e-commerce platforms, and more.

Yes. Only users with specific rights can modify views or add fields. You can also restrict visibility of custom fields to specific groups or departments.

All changes made with Studio or through custom development can be packaged and deployed between staging and production using Noetics’ modular architecture. To ensure stability during upgrades, customizations should follow scoped module logic or use Studio’s safe-edit features. Updates won’t overwrite these changes, and you can test everything in a staging environment before going live.

You can create and track email, social, and SMS campaigns from one pane of glass. Each campaign links to contacts, scheduled activities, and performance metrics like opens and clicks.

For email campaigns use the Email Marketing app to build targeted lists, design emails with a drag-and-drop builder, and schedule sends. You can track open rates, bounce rates, and link clicks in real time.

Campaigns can be linked directly to leads or opportunities. When a contact engages with an email, landing page, form or survey, a lead can be created automatically in the CRM. Sales reps can see the full campaign history and act accordingly.

Yes. Use marketing automation to define flows—like sending an email, waiting for a click, and then creating a task or sending a follow-up message based on behavior.

Yes. You can filter contacts by tags, location, activity history, or any custom field. These segments can be reused across email, SMS, and CRM activities.

The Events app lets you publish event pages, manage ticketing, track registrations, and send reminders. Attendees can be funneled into CRM or email campaigns.

Each campaign shows real-time KPIs: delivery rates, open rates, click-throughs, and bounce stats. You can also link campaigns to revenue in the CRM to calculate ROI.

You can schedule and publish posts across multiple social platforms, monitor engagement, and track results. Each post can be linked to a campaign for centralized reporting. Noetics supports integrations with tools like Google Analytics, Facebook Ads, and external email providers. You can sync contacts, track campaigns, and pull in analytics.

Create reusable templates for emails, landing pages, and events. Control design, tone, and layout so teams stay aligned across all channels.

You can manage job postings, track applicants, schedule interviews, and move candidates through a hiring pipeline—all from one dashboard. Jobs can be created in the Recruitment app with role details, requirements, and locations. You can publish them to your website or external job boards directly from Noetics.

Candidates apply through your website’s careers page. Each application creates an applicant record with a resume, cover letter, and source info.

All applications appear in a kanban view by stage (e.g. New, Interview, Offer). You can drag candidates through stages, log feedback, attach documents, and schedule interviews.

Resumes, references, and notes are attached to the applicant record. Everything stays in one place—searchable and downloadable when needed.

Yes. You can assign users to each position or applicant. Tasks and interviews can be scheduled with calendar integration and reminders for each step.

You can send emails directly from the applicant record. Templates for interview invites, rejections, or next steps ensure consistent communication.

Yes. Applications show the channel they came from, like LinkedIn, company website, or referral, so you can measure which channels work best.

You can configure approval flows for job offers or headcount changes. Hiring managers and HR can review and approve before an offer goes out. Once an applicant is hired, their data can flow directly into the Employee app to start onboarding—reducing re-entry and speeding up setup.

Dashboards show time to hire, number of applicants, source breakdowns, and offer acceptance rates. You can filter by job, stage, or department.

All activity logs, communications, and notes stay on the applicant record. Everyone involved sees the full history and can act without back-and-forth.

You can build surveys with drag-and-drop blocks (text, multiple choice, ratings, matrix, etc.). Once ready, you publish and share them via email, link, or your website.

Recruitment screening, customer feedback, training assessments, employee satisfaction checks, event follow-up, lead qualification, or internal process reviews.

Yes. You can assign points to answers and define success thresholds. Surveys can create leads, assign tasks, or launch automated workflows based on results.

Responses are stored per participant and summarized with charts, filters, and export options. You can analyze trends or view individual answers.

Yes. You can choose whether to collect respondent identity. For internal use, you can restrict access by user group or department.

Yes. Surveys link with CRM (lead qualification), HR (evaluations), Events (feedback), and custom flows. Responses can be stored on contacts, applicants, or tickets.

Surveys can be reused and scheduled manually or through automation. For example, send a customer feedback survey 10 days after delivery, or a quarterly employee check-in.

Branches can be configured using analytic tags or analytic accounts. Each transaction—invoice, payment, journal entry—can be tagged to a branch for granular P&L, cost center tracking, and branch-level reporting.

Yes. Filter all financial reports by analytic account or tag. You can generate Profit & Loss and Trial Balance per branch, compare them side-by-side, or consolidate into one.

You can create separate companies under one environment. Each company has its own:

• Chart of Accounts
• Users and permissions
• Journals
• Warehouses and inventory
• Fiscal positions
• Financial statements

Users can switch between companies or access multiple (with rights). Each transaction is tied to a company.

Yes. You can configure whether records are company-specific or shared. For example, products and partners can be visible across all companies or only within one.

Yes. User permissions control which companies and analytic tags (branches) a user can see or post in. This limits cross-posting and keeps sensitive data secure.

Yes. You can configure rules to automate intercompany sales, purchases, and journal entries. When one company sells to another, Noetics can auto-create the mirrored transaction on both sides.

Parent companies can run consolidated reports across subsidiaries. Noetics supports multi-company Profit & Loss and Balance Sheet, with automatic currency conversion if needed.