Currency Reporting Clause Samples

Currency Reporting. Borrowers shall report value and other Borrowing Base components to Agent in Dollars, and unless expressly provided otherwise, shall deliver financial statements and calculate financial covenants in Dollars.
Currency Reporting. 64 1.9 Rates ................................................................................................................................. 64 1.10 Rounding ........................................................................................................................... 65 1.11 Guarantees/Earn Outs ....................................................................................................... 65 1.12 Limited Condition Acquisitions ........................................................................................ 65 1.13
Currency Reporting. Contractor shall on at least a quarterly basis, review the asset inventory and produce a report that lists the assets that are due to be refreshed or upgraded in the upcoming plan year. Contactor shall provide monthly reports, starting 180 days prior to lease or license expiration date, showing assets to be refreshed and Software to be upgraded. Contractor shall notify the Government monthly of all open agreements related to assets that are retired or will retire within 180 days of the report date. Contractor shall on at least a monthly basis, report on activities toward completion of the Currency Plan.

Related to Currency Reporting

  • Currency and Foreign Transactions Reporting Act The operations of the Company are and have been conducted at all times in compliance with (i) the requirements of the U.S. Treasury Department Office of Foreign Asset Control and (ii) applicable financial recordkeeping and reporting requirements of the Currency and Foreign Transaction Reporting Act of 1970, as amended, including the Money Laundering Control Act of 1986, as amended, the rules and regulations thereunder and any related or similar money laundering statutes, rules, regulations or guidelines, issued, administered or enforced by any Federal governmental agency (collectively, the “Money Laundering Laws”) and no action, suit or proceeding by or before any court or governmental agency, authority or body or any arbitrator involving the Company with respect to the Money Laundering Laws is pending or, to the Company’s knowledge, assuming reasonable inquiry, threatened.

  • Foreign Asset/Account, Exchange Control and Tax Reporting The Participant may be subject to foreign asset/account, exchange control and/or tax reporting requirements as a result of the acquisition, holding and/or transfer of shares of Common Stock or cash (including dividends and the proceeds arising from the sale of shares of Common Stock) derived from his or her participation in the Plan, to and/or from a brokerage/bank account or legal entity located outside the Participant’s country. The applicable laws of the Participant’s country may require that he or she report such accounts, assets, the balances therein, the value thereof and/or the transactions related thereto to the applicable authorities in such country. The Participant acknowledges that he or she is responsible for ensuring compliance with any applicable foreign asset/account, exchange control and tax reporting requirements and should consult his or her personal legal advisor on this matter.

  • Regulatory Reporting ▇▇▇▇▇▇▇ agrees to provide reports to the federal and applicable state authorities, including the SEC, and to the Fund’s auditors. Applicable state authorities are those governmental agencies located in states in which the Fund is registered to sell shares.

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES