Accounting System Requirement Sample Clauses

Accounting System Requirement. The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”
Sample 1Sample 2Sample 3See All (404)
AutoNDA by SimpleDocs
Accounting System Requirement. Consultant shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or GAAP.
Sample 1
Accounting System Requirement. Vendor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or GAAP.
Sample 1

Related to Accounting System Requirement

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Reliability Standard Seller agrees to abide by (i) CPUC General Order No. 167, “Enforcement of Maintenance and Operation Standards for Electric Generating Facilities”, and (ii) all applicable requirements regarding interconnection of the Project, including the requirements of the interconnected Participating Transmission Owner.

  • Accounting Requirements CONTRACTOR shall comply with all applicable COUNTY, State, and Federal accounting laws, rules and regulations. CONTRACTOR shall establish and maintain accounting systems and financial records that accurately account for and reflect all Federal funds received, including all matching funds from the State, COUNTY and any other local or private organizations. CONTRACTOR’S records shall reflect the expenditure and accounting of said funds in accordance with all applicable State laws and procedures for expending and accounting for all funds and receivables, as well as meet the financial management standards in 45 CFR Part 92 and in the Office of Management and Budget 2 CFR Part 200 “Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards.”

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!