TheStandard plan allows you to create up to 1,000 invoices, the Professional plan allows 2,000 invoices, the Premium plan allows 5,000 invoices in a year with Zoho Billing. If you require more invoices, feel free to contact us at
sup...@zohobilling.com.
Yes, Zoho Billing supports team collaboration. You can add up to 3 users by default, each with customizable roles and access levels. Need more users? We offer user add-ons to meet your team's needs and ensure seamless collaboration.
We accept payments via Visa, MasterCard, American Express, and PayPal. Additionally, bank transfer or check transfer is available for yearly subscriptions. For further details, please get in touch with us at
sa...@zohocorp.com.
Yes, there are no binding contracts or commitments. Zoho Billing operates on a pay-as-you-go basis, either monthly or yearly, allowing you to modify your plan as needed. If you ever find yourself unsatisfied with our product or service, you can cancel your subscription at any time and receive a full refund according to our company's refund policy.
DCSA customer agencies are required to complete a FS Form 7600A and FS Form 7600B or a G-Invoicing order to do business with DCSA. These forms record the agreement between the customer agency and DCSA for Intragovernmental Reimbursable, Buy/Sell Activity in accordance with TFM Volume 1, Part 2, Chapter 4700, Appendix 8.
FS FORM 7600A (DCSA prepopulated template)
FS FORM 7600B (DCSA prepopulated template)
The Buyer Order Tracking Number (Obligating Document Number) recorded on the FS Form 7600B or within G-invoicing will need to be provided to DCSA during the initial case submission process to ensure timely and accurate invoicing occurs.
Providing Valid ODN During Case Submission Section. The value provided in the Obligating Document Number field during the case submission process is critical and allows DCSA to apply the associated charges against a current and valid funding agreement.
For general question about DCSA products and services, receiving access to invoice support details on NP2, questions regarding pricing and billing policies, and specific questions regarding Background Investigation (BI) case billing details.
For questions about your IPAC payments/processing or to dispute an IPAC/payment/case. Also, for questions about the LOA (line of accounting) associated with your orders or to update the agreement obligating document number (ODN)/LOA information associated with a specific order.
Customer agencies are required to ensure that accurate Submitting Office Number (SON), Security Office Identifier (SOI), Agency Location Code (ALC), Obligating Document Number (FS Form 7600B Buyer Order Tracking Number or G-invoicing Order Number), and any other internally required billing information are provided during the initial investigative submission to DCSA.
The SON is required to investigative requests. DCSA assigns a unique four-character alphanumeric code, known as the Submitting Office Number (SON), to each office that requests investigations from DCSA. The SON identifies the office that initiates the investigation and is recorded in the appropriate Agency Use Block (AUB) of the standard form.
The SOI is required for all investigative requests. Each security office is issued a unique alphanumeric four-character identifier from DCSA, the Security Office Identifier (SOI), which is used to identify the appropriate agency official who will receive case results, data, or other information from DCSA.
The accounting data field is an optional field (25-character limit). This block can be used by the requesting agency to note any information that the agency needs for its own internal processes, such as an internal case number, line of accounting, or any other specific agency identifier. This field will appear on your monthly invoice and can be useful for internal invoice reconciliation.
Special note on electronic fingerprint - only case submissions made to DCSA Fingerprint submissions must be sent to DCSA before requesting an associated higher-level investigation that requires fingerprints. Special Agreement Check (SAC) results can be used (and have historically been used by some agencies) to satisfy fingerprint requirements for a higher-level investigation request for up to 120 days.
When an electronic fingerprint-only SAC is submitted, DCSA will hold off on billing for 120 days. If a higher-level case is submitted, the agency will not receive a separate bill for the SAC. As a result, the higher-level case will also no longer receive a corresponding fingerprint SAC credit. If no higher-level case is submitted within 120 days, the SAC will be billed to the agency as a standalone charge.
Since not all electronic fingerprint machines contain an accounting field, the Attention Indicator, "ATN" field, can be used as an alternative method on most machines. Populated ATN field details will return in the "Accounting" field within the monthly invoices. This process can be used as an effective alternative to provide agency required accounting or requesting official contact details that are otherwise not commonly available with fingerprint submissions. Additionally, the Occupation, "OCP" field, can be used to return agency, requesting office, and/or subject specific identifiers. Populated OCP field details will return in the "POSITION" field on monthly invoices. Agencies using GSA shared enrollment (USAccess) centers may not have the ability to populate the ATN and OCP fields. Agencies using USAccess should address their concerns regarding this and/or issues with "missing" accounting details on their invoice(s) directly with GSA. The field requirements for the ATN field are: populated with greater than 3 characters; truncated at 30 characters; and cannot contain any dot or "special" characters. The only field requirement for the OCP field is that it will be truncated at 50 characters.
Requirements for Submitting Reprints when Prints are Unclassifiable. When the FBI is unable to make a classifiable determination due to illegible fingerprints, the FBI deems the submissions as "Unclassifiable". A reprint may be submitted within one year of the case closing date to obtain a classifiable determination without incurring additional cost. The original case number of the unclassifiable fingerprint must be provided with the reprint submission to avoid the discontinuance of the reprint or an additional fingerprint processing charge. The original case number must be provided in the OCA block on the SF-87 or FD-258 hard card or in the tagged field 2.009 of the electronic transmission. When submitting a hard card, please note "Reprint" in the top left-hand corner and attach the Notice of Unclassifiable Fingerprints.
Customer agencies must provide accurate and financial codes and agency identifiers during the initial investigative submission to DCSA. This includes: Submitting Office Number (SON), Security Office Identifier (SOI), Agency Location Code (ALC), Obligating Document Number (FS Form 7600B Order Tracking Number), Line of Accounting, and any other internally required billing information.
Adjustment made for Processing Fee when Child Care cases add a State Criminal History Repository (SCHR) search as additional coverage (there may be an AD event for each search conducted)
Adjustment made when named-based searches of FBI Criminal and Investigative Files for subject spouses and/or cohabitants are conducted on lower level cases with Access Levels 3-5 (there may be an AP event for each search conducted, this is possible when a person has had multiple last names)
Adjustment made for processing fee when a Bar Association License Checks is added as additional coverage or is conducted on a SAC product (there may be an AY event for each state search conducted)
You can allocate your costs to teams, applications, or environments by using cost categories or cost allocation tags, or using AWS Cost Explorer. You can also export data to your preferred data warehouse or business intelligence tool.
Billing Conductor is a custom billing service that supports the showback and chargeback workflows of AWS Solution Providers and AWS Enterprise customers. You can customize a second, alternative version of your monthly billing data. The service models the billing relationship between you and your customers or business units.
Billing Conductor doesn't change the way that you're billed by AWS each month. Instead, you can use the service to configure, generate, and display rates to specific customers over a given billing period. You can also use it to analyze the difference between the rates that you apply to your groupings relative to the actual rates for those same accounts from AWS.
As a result of your Billing Conductor configuration, the payer account (management account) can also see the custom rate that's applied on the billing details page of the AWS Billing and Cost Management console. The payer account can also configure AWS Cost and Usage Reports per billing group.
You can use AWS Identity and Access Management (IAM) to control who in your account or organization has access to specific pages on the Billing and Cost Management console. For example, you can control access to invoices and detailed information about charges and account activity, budgets, payment methods, and credits. IAM is a feature of your AWS account. You don't need to do anything else to sign up for IAM and there's no charge to use it.
When you create an account, you begin with one sign-in identity that has complete access to all AWS services and resources in the account. This identity is called the AWS account root user and is accessed by signing in with the email address and password that you used to create the account. We strongly recommend that you don't use the root user for your everyday tasks. Safeguard your root user credentials and use them to perform the tasks that only the root user can perform.
3a8082e126